Server Maintenance

How can I fix NoClassDefFoundErrors on the SAX classes?
If you see errors like this mananging WAS 5.1:
was5:stopServer:
    [stopServer] ADMU0116I: Tool information is being logged in file c:\Program
    [stopServer]            Files\WebSphere\AppServer\logs\server1\stopServer.log
    [stopServer] ADMU3100I: Reading configuration for server: server1
    [stopServer] ADMU0111E: Program exiting with error: java.lang.NoClassDefFoundError:
    [stopServer]            org/xml/sax/helpers/DefaultHandler
    [stopServer] ADMU0211I: Error details may be seen in the file: c:\Program
    [stopServer]            Files\WebSphere\AppServer\logs\server1\stopServer.log
    [stopServer] ADMU1211I: To obtain a full trace of the failure, use the -trace option.
    [stopServer] [ERROR] Java Result: 111
        

This means you are using a 1.3 JDK rather than the 1.4 JDK shipped with AppServer 5.1.



Generating EJB Code

How do I fix errors about missing IBM classes?

If you see something like this:

[wasEjbDeploy] [*Error] /general-ejb-1.0-SNAPSHOT: The project was not built since its classpath is incomplete. 
Cannot find the class file for com.ibm.CORBA.iiop.ObjectResolver. 
Fix the classpath then try rebuilding this project.

It's usually because you are using a JDK other than the IBM JDK shipped with AppServer. Usually it's enough to set JAVA_HOME to something like C:\Program Files\WebSphere\AppServer\java