DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29258>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29258 Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH Summary: Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH Product: Tomcat 5 Version: 5.0.24 Platform: Sun OS/Version: Solaris Status: NEW Severity: Minor Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When you upgrade an existing Tomcat 5.0.19 server to Tomcat 5.0.24+, you may have problems getting the server to come up without adding jmx.jar explicitly to the CLASSPATH. This happens only after a badly applied upgrade. The "fix" to make sure this doesn't happen is to add jmx.jar to the CLASSPATH after commons-logging-api.jar. Without this fix, you may see this message in catalina.out: Bootstrap: Class loader creation threw exception java.lang.NoClassDefFoundError: javax/management/MBeanServerFactory at org.apache.catalina.startup.Bootstrap.createClassLoader (Bootstrap.java:165) at org.apache.catalina.startup.Bootstrap.initClassLoaders (Bootstrap.java:104) at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:193) at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:270) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.daemon.support.DaemonLoader.load (DaemonLoader.java:201) Since you can fix the configuration problem in the server, adding jmx.jar explicitly to the CLASSPATH is a minor bug fix, although it might provide a big hint to people who are upgrading Tomcat 5.0.19 servers. Typically this error means someone may have moved jmx.jar to its previous resting place (i.e., $CATALINA_HOME/common/lib) because they thought that's where it was supposed to go, so you can just restore a correct copy of jmx.jar to bin to recover from this problem. This could be avoided by a documentation update instead of a code change. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
