Error unregistering mbean
Last night we upgraded our JVM from 1.4 to 1.5. After the upgrade, the server still works, however we're getting an exception thrown repeatedly: - Error unregistering mbean javax.management.RuntimeOperationsException: Object name cannot be null at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered( DefaultMBeanServerInterceptor.java:545) at com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered( JmxMBeanServer.java:619) at org.apache.commons.modeler.Registry.unregisterComponent( Registry.java:642) at org.apache.jk.common.ChannelSocket.processConnection( ChannelSocket.java:706) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java :866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: Object name cannot be null ... 7 more We're running Tomcat 5.0, Apache 2.0 with jk_mod against a sybase db. The only change was the JVM and our webapp compiled in 1.5. Any ideas where to start looking??? Todd -- -- The only dumb question is the one you were too afraid to ask. Check out RouteRuler - Free software for runners, cyclists, walkers, etc. http://routeruler.sourceforge.net
Re: Error unregistering mbean
You may consider upgrading from Tomcat 5.0 to Tomcat 5.5. + It implements the same version of the specification (Servlets 2.4/JSP 2.0), thus there must be no impact for your webapp. + It is designed to run on JVM 1.5 in its default configuration. (Running with JVM 1.4 requires additional components). See Dependency Changes in http://tomcat.apache.org/tomcat-5.5-doc/RELEASE-NOTES.txt + It is actively supported. 2007/10/16, todd runstein [EMAIL PROTECTED]: Last night we upgraded our JVM from 1.4 to 1.5. After the upgrade, the server still works, however we're getting an exception thrown repeatedly: - Error unregistering mbean javax.management.RuntimeOperationsException: Object name cannot be null at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered( DefaultMBeanServerInterceptor.java:545) at com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered( JmxMBeanServer.java:619) at org.apache.commons.modeler.Registry.unregisterComponent( Registry.java:642) at org.apache.jk.common.ChannelSocket.processConnection( ChannelSocket.java:706) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java :866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: Object name cannot be null ... 7 more We're running Tomcat 5.0, Apache 2.0 with jk_mod against a sybase db. The only change was the JVM and our webapp compiled in 1.5. Any ideas where to start looking??? Todd -- -- The only dumb question is the one you were too afraid to ask. Check out RouteRuler - Free software for runners, cyclists, walkers, etc. http://routeruler.sourceforge.net - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error unregistering mbean
Yup, upgrading is probably the best answer. Depending on which version of 5.0 you have, you might also be able to work around it by setting request.registerRequests=false on the Connector / element in server.xml. In any case, the error is harmless, besides taking up space in the log file. Konstantin Kolinko [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] You may consider upgrading from Tomcat 5.0 to Tomcat 5.5. + It implements the same version of the specification (Servlets 2.4/JSP 2.0), thus there must be no impact for your webapp. + It is designed to run on JVM 1.5 in its default configuration. (Running with JVM 1.4 requires additional components). See Dependency Changes in http://tomcat.apache.org/tomcat-5.5-doc/RELEASE-NOTES.txt + It is actively supported. 2007/10/16, todd runstein [EMAIL PROTECTED]: Last night we upgraded our JVM from 1.4 to 1.5. After the upgrade, the server still works, however we're getting an exception thrown repeatedly: - Error unregistering mbean javax.management.RuntimeOperationsException: Object name cannot be null at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered( DefaultMBeanServerInterceptor.java:545) at com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered( JmxMBeanServer.java:619) at org.apache.commons.modeler.Registry.unregisterComponent( Registry.java:642) at org.apache.jk.common.ChannelSocket.processConnection( ChannelSocket.java:706) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java :866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: Object name cannot be null ... 7 more We're running Tomcat 5.0, Apache 2.0 with jk_mod against a sybase db. The only change was the JVM and our webapp compiled in 1.5. Any ideas where to start looking??? Todd -- -- The only dumb question is the one you were too afraid to ask. Check out RouteRuler - Free software for runners, cyclists, walkers, etc. http://routeruler.sourceforge.net - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SEVERE: Error unregistering mbean
I am running Apache 2.0.52, jk2 2.0.4, and Tomcat 5.0.28. Recently I changed the version of Java that Tomcat is using from IBM jdk 1.4.1 to Sun jdk 1.6. Since then I get the following messages in the catalina.out file every 5 minutes or so: Mar 20, 2007 11:59:46 AM org.apache.commons.modeler.Registry unregisterComponent SEVERE: Error unregistering mbean javax.management.RuntimeOperationsException: Object name cannot be null at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:582) at com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:598) at org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:642) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:706) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: Object name cannot be null ... 7 more Can anyone suggest a fix for this? Thanks, Nathan - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Greetings. I found in Google this posting http://mail-archives.apache.org/mod_mbox/jakarta-tomcat-user/200411.mbox/[EMAIL PROTECTED] I have the same problem with Tomcat 5.0.28 Is there a solution? Maybe it has been fixed? Thank you - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
