V5.0 nodeagent fails to start due to java.lang.NoClassDefFoundError: com/ibm/logging/LoggerCfg after upgrading the IBM Java 2 SDK
 Technote (troubleshooting)
 
Problem(Abstract)
After upgrading the IBM® Java™ 2 SDK for V5.0, the following exception is logged to SystemOut.log:

WSVR0003E: Server nodeagent failed to start with a nested exception of
---- Begin backtrace for nested exception
java.lang.NoClassDefFoundError: com/ibm/logging/LoggerCfg
at com.tivoli.jmx.utils.logging.CatUtil.createJmxCatalog(CatUtil.java:76)
at com.tivoli.jmx.utils.logging.CatUtil.<clinit>(CatUtil.java:32)
at com.tivoli.jmx.utils.logging.LogUtil.<clinit>(LogUtil.java:36)
at javax.management.ObjectName.<init>(ObjectName.java:194)
 
Cause
This error is due to a missing log.jar file. This file is supposed to be located in the install_root /update/java/jre/lib/ext directory.
The most likely cause of the problem is that the SDK upgrade was not done properly. The latest SDK upgrade instructions say to copy the existing Java directory rather than moving it. The log.jar is usually not replaced by the upgrade. The instructions assume that the previous version is still there.

To determine if this is the cause of this message:

  1. Verify that the log.jar file is in the install_root /update/java/jre/lib/ext directory.

  2. Verify that the correct permissions are set on the file.
 
Resolving the problem
Compare the files in the backed-up Java directory. If the error is due to one or more missing log.jar files, copy the missing files to the JDK™ upgrade.
To avoid the problem, rerun the SDK upgrade.
 
 
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 > Java SDK
Operating system(s): z/OS
Software version: 5.0.2.5
Software edition:
Reference #: 1173701
IBM Group: Software Group
Modified date: Aug 18, 2004