Application server fails to start after fix pack is installed

Technote (FAQ)
Problem
If you have previously applied a temporary fix by placing a file or files in the $WAS_HOME/classes directory, you must remove these files after installing the fix pack containing this fix. If you do not remove the temporary fix files, the application server might not start after applying the fix pack. One such known temporary fix will result in a NoClassDefFound on etools/emf/RefBaseObject error.
Cause
The classes directory will override the corrected class file delivered with the fix pack. The installer will remove PQ fixes that have been installed and registered as a PQ fix that has been applied. The installer will not remove temporary fixes from the classes directory.
Solution
Verify that the temporary fix has been rolled into the new fix pack by reviewing the defects corrected by the fix pack. If found in the list of defects corrected, then delete the temporary fix from the $WAS_HOME/classes directory. Then apply the fix pack.

Another way to avoid this situation is to get the published fix from the support site, install the published fix and then remove the temporary fix. Now the installer will see this fix and remove it before applying the fix pack.

Related information
PMI has the same request to remove Preview jar












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Install
Operating system(s): Multi-Platform
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Edition Independent
Reference #: 1162328
IBM Group: Software Group
Modified date: 2004-03-03