Node agent fails to start after wrong class is loaded from unsupported version of xerces.jar
 Technote (troubleshooting)
 
Problem(Abstract)
Placing an unsupported version of xerces.jar, containing its own version of the class org.xml.sax.helpers.XMLReaderFactory, in your $WAS_HOME/java/jre/lib/ext directory can generate unexpected results.
 
Cause
Providing a newer version of the xerces.jar file could cause its XMLReaderFactory class to be loaded instead of the version of this class that ships with WebSphere® Application Server (located in $WAS_HOME/lib/j2ee.jar). This causes a starting failure of your node agent. The failure to start results in error messages similar to the following being logged to your native_stdout.log file.
 
Resolving the problem
Make sure the following directories contain only the correct file versions that ship with WebSphere Application Server:
  • $WAS_HOME/java/lib
  • $WAS_HOME/java/jre/lib
  • $WAS_HOME/java/jre/lib/ext
  • $WAS_HOME/lib

If you place any files in the $WAS_HOME/classes directory, make sure they are not replacing or overriding essential product files.

To solve the problem described above, make sure that your XMLReaderFactory.class file in the $WAS_HOME/lib directory is the correct and only version that is loaded.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Servlet Engine/Web Container
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1105483
IBM Group: Software Group
Modified date: Mar 4, 2004