RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi, Bill already fixed it I think .. " Thanks for the report. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=81697 "Allistair Crossley" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Yoav, Has this one been noted by your good self for invesigation or propogation to the appropriate place? It's still all over our logs. " Allistair > -Original Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 23 November 2004 12:42 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > > Hi, > Well, it was noted briefly and then forgotten in my flurry of fixing > things for 5.0.30. Please open a Bugzilla item so that neither I nor > any other committers forget this again. Thanks, > > Yoav Shapira http://www.yoavshapira.com > > > >-Original Message- > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, November 23, 2004 4:28 AM > >To: Tomcat Users List > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >mins. > > > >Yoav, > > > >Has this one been noted by your good self for invesigation or > propogation > >to the appropriate place? It's still all over our logs. > > > >Allistair > > > >> -Original Message- > >> From: Allistair Crossley > >> Sent: 19 November 2004 14:47 > >> To: Tomcat Users List > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > stdout every > >> 5-10 mins. > >> > >> > >> Hi > >> > >> OK, ran an e-Load script covering home page (database query > >> heavy), 2 navigations (medium) and 1 full text search. Under > >> a load of 50 virtual users (started at same time) * 2 > >> iterations of the script, this produces more load then normal > >> usage. No errors at all from the test Tomcat. Hm. > >> > >> Allistair. > >> > >> > -Original Message- > >> > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> > Sent: 19 November 2004 14:19 > >> > To: Tomcat Users List > >> > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout > every > >> > 5-10 mins. > >> > > >> > > >> > > >> > Hi, > >> > The next step, then, is to run a stress test in your test > >> environment. > >> > See if you get the same errors. > >> > > >> > Yoav Shapira http://www.yoavshapira.com > >> > > >> > > >> > >-Original Message- > >> > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >> > >Sent: Friday, November 19, 2004 8:45 AM > >> > >To: Tomcat Users List > >> > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > >> stdout every > >> > 5-10 > >> > >mins. > >> > > > >> > >Hi Yoav, > >> > > > >> > >Tomcat standalone no. > >> > > > >> > >IIS > Tomcat > SQL Server > >> > > > Content Management System > >> > > > >> > >However, we have the same setup on test and production > >> > servers and test > >> > >does not exhibit this behaviour, perhaps due to load, or so on I > >> > expect. > >> > > > >> > >Cheers, Allistair > >> > > > >> > >> -Original Message- > >> > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> > >> Sent: 19 November 2004 13:38 > >> > >> To: Tomcat Users List > >> > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > >> > stdout every > >> > >> 5-10 mins. > >> > >> > >> > >> > >> > >> > >> > >> Hi, > >> > >> I think I already know the answer to this, but I'll ask > >> > >> anyways: does it > >> > >> happen with Tomcat standalone? My guess is no. > >> > >> > >> > >> Yoav Shapira http://www.yoavshapira.com > >> > >> > >> > >> > >> > >> >-Original Message- > >> > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >> > >> >Sent: Friday, November 19, 2004 6:32 AM > >> > >> >To: [EMAIL PRO
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi, Well, it was noted briefly and then forgotten in my flurry of fixing things for 5.0.30. Please open a Bugzilla item so that neither I nor any other committers forget this again. Thanks, Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Allistair Crossley [mailto:[EMAIL PROTECTED] >Sent: Tuesday, November 23, 2004 4:28 AM >To: Tomcat Users List >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 >mins. > >Yoav, > >Has this one been noted by your good self for invesigation or propogation >to the appropriate place? It's still all over our logs. > >Allistair > >> -Original Message- >> From: Allistair Crossley >> Sent: 19 November 2004 14:47 >> To: Tomcat Users List >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every >> 5-10 mins. >> >> >> Hi >> >> OK, ran an e-Load script covering home page (database query >> heavy), 2 navigations (medium) and 1 full text search. Under >> a load of 50 virtual users (started at same time) * 2 >> iterations of the script, this produces more load then normal >> usage. No errors at all from the test Tomcat. Hm. >> >> Allistair. >> >> > -Original Message- >> > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >> > Sent: 19 November 2004 14:19 >> > To: Tomcat Users List >> > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every >> > 5-10 mins. >> > >> > >> > >> > Hi, >> > The next step, then, is to run a stress test in your test >> environment. >> > See if you get the same errors. >> > >> > Yoav Shapira http://www.yoavshapira.com >> > >> > >> > >-Original Message- >> > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] >> > >Sent: Friday, November 19, 2004 8:45 AM >> > >To: Tomcat Users List >> > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in >> stdout every >> > 5-10 >> > >mins. >> > > >> > >Hi Yoav, >> > > >> > >Tomcat standalone no. >> > > >> > >IIS > Tomcat > SQL Server >> > > > Content Management System >> > > >> > >However, we have the same setup on test and production >> > servers and test >> > >does not exhibit this behaviour, perhaps due to load, or so on I >> > expect. >> > > >> > >Cheers, Allistair >> > > >> > >> -Original Message- >> > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >> > >> Sent: 19 November 2004 13:38 >> > >> To: Tomcat Users List >> > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in >> > stdout every >> > >> 5-10 mins. >> > >> >> > >> >> > >> >> > >> Hi, >> > >> I think I already know the answer to this, but I'll ask >> > >> anyways: does it >> > >> happen with Tomcat standalone? My guess is no. >> > >> >> > >> Yoav Shapira http://www.yoavshapira.com >> > >> >> > >> >> > >> >-Original Message- >> > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] >> > >> >Sent: Friday, November 19, 2004 6:32 AM >> > >> >To: [EMAIL PROTECTED] >> > >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every >> > 5-10 >> > >> mins. >> > >> > >> > >> >Hi, >> > >> > >> > >> >Having run our web application on 5.5.4 for a couple of >> > days, I have >> > >> >studied the stdout logs to find that we are getting >> severe errors >> > >> relating >> > >> >to mbeans. Here are some time intervals: >> > >> > >> > >> >10:43 >> > >> >11:10 >> > >> >11:14 >> > >> >11:24 >> > >> > >> > >> >This time pattern stays fairly consistent as above. >> > >> > >> > >> >Each time the errors occur, they appear as a set as >> follows below. >> > >> > >> > >> >Can I do anything to prevent this? >> > >> > >> > >> >Cheers, Allistair. >> > >>
Re: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Thanks for the report. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=81697 "Allistair Crossley" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Yoav, Has this one been noted by your good self for invesigation or propogation to the appropriate place? It's still all over our logs. Allistair > -Original Message- > From: Allistair Crossley > Sent: 19 November 2004 14:47 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > Hi > > OK, ran an e-Load script covering home page (database query > heavy), 2 navigations (medium) and 1 full text search. Under > a load of 50 virtual users (started at same time) * 2 > iterations of the script, this produces more load then normal > usage. No errors at all from the test Tomcat. Hm. > > Allistair. > > > -Original Message- > > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > > Sent: 19 November 2004 14:19 > > To: Tomcat Users List > > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > > 5-10 mins. > > > > > > > > Hi, > > The next step, then, is to run a stress test in your test > environment. > > See if you get the same errors. > > > > Yoav Shapira http://www.yoavshapira.com > > > > > > >-Original Message- > > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > > >Sent: Friday, November 19, 2004 8:45 AM > > >To: Tomcat Users List > > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > stdout every > > 5-10 > > >mins. > > > > > >Hi Yoav, > > > > > >Tomcat standalone no. > > > > > >IIS > Tomcat > SQL Server > > > > Content Management System > > > > > >However, we have the same setup on test and production > > servers and test > > >does not exhibit this behaviour, perhaps due to load, or so on I > > expect. > > > > > >Cheers, Allistair > > > > > >> -Original Message- > > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > > >> Sent: 19 November 2004 13:38 > > >> To: Tomcat Users List > > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > > stdout every > > >> 5-10 mins. > > >> > > >> > > >> > > >> Hi, > > >> I think I already know the answer to this, but I'll ask > > >> anyways: does it > > >> happen with Tomcat standalone? My guess is no. > > >> > > >> Yoav Shapira http://www.yoavshapira.com > > >> > > >> > > >> >-Original Message- > > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > > >> >Sent: Friday, November 19, 2004 6:32 AM > > >> >To: [EMAIL PROTECTED] > > >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every > > 5-10 > > >> mins. > > >> > > > >> >Hi, > > >> > > > >> >Having run our web application on 5.5.4 for a couple of > > days, I have > > >> >studied the stdout logs to find that we are getting > severe errors > > >> relating > > >> >to mbeans. Here are some time intervals: > > >> > > > >> >10:43 > > >> >11:10 > > >> >11:14 > > >> >11:24 > > >> > > > >> >This time pattern stays fairly consistent as above. > > >> > > > >> >Each time the errors occur, they appear as a set as > follows below. > > >> > > > >> >Can I do anything to prevent this? > > >> > > > >> >Cheers, Allistair. > > >> > > > >> >SEVERE: Error unregistering mbean > > >> >javax.management.RuntimeOperationsException: Object name > > >> cannot be null > > >> > at > > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > > >> tered(Defa > > >> ultM > > >> >BeanServerInterceptor.java:545) > > >> > at > > >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > > >> erver.java > > >> :619 > > >> >) > > >> > at > > >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis > > >> try.java:6 > > >> 42) > > >> > at > > >> >org.ap
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Yoav, Has this one been noted by your good self for invesigation or propogation to the appropriate place? It's still all over our logs. Allistair > -Original Message- > From: Allistair Crossley > Sent: 19 November 2004 14:47 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > Hi > > OK, ran an e-Load script covering home page (database query > heavy), 2 navigations (medium) and 1 full text search. Under > a load of 50 virtual users (started at same time) * 2 > iterations of the script, this produces more load then normal > usage. No errors at all from the test Tomcat. Hm. > > Allistair. > > > -Original Message- > > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > > Sent: 19 November 2004 14:19 > > To: Tomcat Users List > > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > > 5-10 mins. > > > > > > > > Hi, > > The next step, then, is to run a stress test in your test > environment. > > See if you get the same errors. > > > > Yoav Shapira http://www.yoavshapira.com > > > > > > >-Original Message- > > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > > >Sent: Friday, November 19, 2004 8:45 AM > > >To: Tomcat Users List > > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > stdout every > > 5-10 > > >mins. > > > > > >Hi Yoav, > > > > > >Tomcat standalone no. > > > > > >IIS > Tomcat > SQL Server > > > > Content Management System > > > > > >However, we have the same setup on test and production > > servers and test > > >does not exhibit this behaviour, perhaps due to load, or so on I > > expect. > > > > > >Cheers, Allistair > > > > > >> -Original Message- > > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > > >> Sent: 19 November 2004 13:38 > > >> To: Tomcat Users List > > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > > stdout every > > >> 5-10 mins. > > >> > > >> > > >> > > >> Hi, > > >> I think I already know the answer to this, but I'll ask > > >> anyways: does it > > >> happen with Tomcat standalone? My guess is no. > > >> > > >> Yoav Shapira http://www.yoavshapira.com > > >> > > >> > > >> >-Original Message- > > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > > >> >Sent: Friday, November 19, 2004 6:32 AM > > >> >To: [EMAIL PROTECTED] > > >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every > > 5-10 > > >> mins. > > >> > > > >> >Hi, > > >> > > > >> >Having run our web application on 5.5.4 for a couple of > > days, I have > > >> >studied the stdout logs to find that we are getting > severe errors > > >> relating > > >> >to mbeans. Here are some time intervals: > > >> > > > >> >10:43 > > >> >11:10 > > >> >11:14 > > >> >11:24 > > >> > > > >> >This time pattern stays fairly consistent as above. > > >> > > > >> >Each time the errors occur, they appear as a set as > follows below. > > >> > > > >> >Can I do anything to prevent this? > > >> > > > >> >Cheers, Allistair. > > >> > > > >> >SEVERE: Error unregistering mbean > > >> >javax.management.RuntimeOperationsException: Object name > > >> cannot be null > > >> >at > > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > > >> tered(Defa > > >> ultM > > >> >BeanServerInterceptor.java:545) > > >> >at > > >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > > >> erver.java > > >> :619 > > >> >) > > >> >at > > >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis > > >> try.java:6 > > >> 42) > > >> >at > > >> >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > > >> ocket.java > > >> :706 > > >>
5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi OK, ran an e-Load script covering home page (database query heavy), 2 navigations (medium) and 1 full text search. Under a load of 50 virtual users (started at same time) * 2 iterations of the script, this produces more load then normal usage. No errors at all from the test Tomcat. Hm. Allistair. > -Original Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 19 November 2004 14:19 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > > Hi, > The next step, then, is to run a stress test in your test environment. > See if you get the same errors. > > Yoav Shapira http://www.yoavshapira.com > > > >-Original Message- > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >Sent: Friday, November 19, 2004 8:45 AM > >To: Tomcat Users List > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >mins. > > > >Hi Yoav, > > > >Tomcat standalone no. > > > >IIS > Tomcat > SQL Server > > > Content Management System > > > >However, we have the same setup on test and production > servers and test > >does not exhibit this behaviour, perhaps due to load, or so on I > expect. > > > >Cheers, Allistair > > > >> -----Original Message- > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> Sent: 19 November 2004 13:38 > >> To: Tomcat Users List > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > stdout every > >> 5-10 mins. > >> > >> > >> > >> Hi, > >> I think I already know the answer to this, but I'll ask > >> anyways: does it > >> happen with Tomcat standalone? My guess is no. > >> > >> Yoav Shapira http://www.yoavshapira.com > >> > >> > >> >-Original Message- > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >> >Sent: Friday, November 19, 2004 6:32 AM > >> >To: [EMAIL PROTECTED] > >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >> mins. > >> > > >> >Hi, > >> > > >> >Having run our web application on 5.5.4 for a couple of > days, I have > >> >studied the stdout logs to find that we are getting severe errors > >> relating > >> >to mbeans. Here are some time intervals: > >> > > >> >10:43 > >> >11:10 > >> >11:14 > >> >11:24 > >> > > >> >This time pattern stays fairly consistent as above. > >> > > >> >Each time the errors occur, they appear as a set as follows below. > >> > > >> >Can I do anything to prevent this? > >> > > >> >Cheers, Allistair. > >> > > >> >SEVERE: Error unregistering mbean > >> >javax.management.RuntimeOperationsException: Object name > >> cannot be null > >> > at > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > >> tered(Defa > >> ultM > >> >BeanServerInterceptor.java:545) > >> > at > >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > >> erver.java > >> :619 > >> >) > >> > at > >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis > >> try.java:6 > >> 42) > >> > at > >> >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > >> ocket.java > >> :706 > >> >) > >> > at > >> > >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) > >> > at > >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > >> (ThreadPoo > >> l.ja > >> >va:684) > >> > at java.lang.Thread.run(Thread.java:595) > >> >Caused by: java.lang.IllegalArgumentException: Object > name cannot be > >> null > >> > ... 7 more > >> >19-Nov-2004 10:43:47 org.apache.commons.modeler.Registry > >> >unregisterComponent > >> >SEVERE: Error unregistering mbean > >> >javax.management.RuntimeOperationsException: Object name > >> cannot be null > >> > at > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > >> tered(Defa > >> ultM > >> >BeanServerInterceptor.java:545) > >> > at > &
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi OK, ran an e-Load script covering home page (database query heavy), 2 navigations (medium) and 1 full text search. Under a load of 50 virtual users (started at same time) * 2 iterations of the script, this produces more load then normal usage. No errors at all from the test Tomcat. Hm. Allistair. > -Original Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 19 November 2004 14:19 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > > Hi, > The next step, then, is to run a stress test in your test environment. > See if you get the same errors. > > Yoav Shapira http://www.yoavshapira.com > > > >-Original Message- > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >Sent: Friday, November 19, 2004 8:45 AM > >To: Tomcat Users List > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >mins. > > > >Hi Yoav, > > > >Tomcat standalone no. > > > >IIS > Tomcat > SQL Server > > > Content Management System > > > >However, we have the same setup on test and production > servers and test > >does not exhibit this behaviour, perhaps due to load, or so on I > expect. > > > >Cheers, Allistair > > > >> -----Original Message- > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> Sent: 19 November 2004 13:38 > >> To: Tomcat Users List > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > stdout every > >> 5-10 mins. > >> > >> > >> > >> Hi, > >> I think I already know the answer to this, but I'll ask > >> anyways: does it > >> happen with Tomcat standalone? My guess is no. > >> > >> Yoav Shapira http://www.yoavshapira.com > >> > >> > >> >-Original Message- > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >> >Sent: Friday, November 19, 2004 6:32 AM > >> >To: [EMAIL PROTECTED] > >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >> mins. > >> > > >> >Hi, > >> > > >> >Having run our web application on 5.5.4 for a couple of > days, I have > >> >studied the stdout logs to find that we are getting severe errors > >> relating > >> >to mbeans. Here are some time intervals: > >> > > >> >10:43 > >> >11:10 > >> >11:14 > >> >11:24 > >> > > >> >This time pattern stays fairly consistent as above. > >> > > >> >Each time the errors occur, they appear as a set as follows below. > >> > > >> >Can I do anything to prevent this? > >> > > >> >Cheers, Allistair. > >> > > >> >SEVERE: Error unregistering mbean > >> >javax.management.RuntimeOperationsException: Object name > >> cannot be null > >> > at > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > >> tered(Defa > >> ultM > >> >BeanServerInterceptor.java:545) > >> > at > >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > >> erver.java > >> :619 > >> >) > >> > at > >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis > >> try.java:6 > >> 42) > >> > at > >> >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > >> ocket.java > >> :706 > >> >) > >> > at > >> > >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) > >> > at > >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > >> (ThreadPoo > >> l.ja > >> >va:684) > >> > at java.lang.Thread.run(Thread.java:595) > >> >Caused by: java.lang.IllegalArgumentException: Object > name cannot be > >> null > >> > ... 7 more > >> >19-Nov-2004 10:43:47 org.apache.commons.modeler.Registry > >> >unregisterComponent > >> >SEVERE: Error unregistering mbean > >> >javax.management.RuntimeOperationsException: Object name > >> cannot be null > >> > at > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > >> tered(Defa > >> ultM > >> >BeanServerInterceptor.java:545) > >> > at > &
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi, >I am guessing you don't know why this is happening? That guess is right, and then some. As you might know by now, I don't care to spend my time on connector issues. >or are you just trying >to get me to get this tested in another environment so you know to take it >seriously ;) ? No, that's not right. I was suggesting the generic next step, which is to reproduce the bug in your test environment. If you can't do that, not much else will be helpful. In your specific case, I take it pretty seriously actually ;) Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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.
Hi Yoav, I am guessing you don't know why this is happening? or are you just trying to get me to get this tested in another environment so you know to take it seriously ;) ? Cheers! Allistair. > -Original Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 19 November 2004 14:19 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > > Hi, > The next step, then, is to run a stress test in your test environment. > See if you get the same errors. > > Yoav Shapira http://www.yoavshapira.com > > > >-Original Message- > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >Sent: Friday, November 19, 2004 8:45 AM > >To: Tomcat Users List > >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >mins. > > > >Hi Yoav, > > > >Tomcat standalone no. > > > >IIS > Tomcat > SQL Server > > > Content Management System > > > >However, we have the same setup on test and production > servers and test > >does not exhibit this behaviour, perhaps due to load, or so on I > expect. > > > >Cheers, Allistair > > > >> -----Original Message- > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> Sent: 19 November 2004 13:38 > >> To: Tomcat Users List > >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in > stdout every > >> 5-10 mins. > >> > >> > >> > >> Hi, > >> I think I already know the answer to this, but I'll ask > >> anyways: does it > >> happen with Tomcat standalone? My guess is no. > >> > >> Yoav Shapira http://www.yoavshapira.com > >> > >> > >> >-Original Message- > >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >> >Sent: Friday, November 19, 2004 6:32 AM > >> >To: [EMAIL PROTECTED] > >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 > >> mins. > >> > > >> >Hi, > >> > > >> >Having run our web application on 5.5.4 for a couple of > days, I have > >> >studied the stdout logs to find that we are getting severe errors > >> relating > >> >to mbeans. Here are some time intervals: > >> > > >> >10:43 > >> >11:10 > >> >11:14 > >> >11:24 > >> > > >> >This time pattern stays fairly consistent as above. > >> > > >> >Each time the errors occur, they appear as a set as follows below. > >> > > >> >Can I do anything to prevent this? > >> > > >> >Cheers, Allistair. > >> > > >> >SEVERE: Error unregistering mbean > >> >javax.management.RuntimeOperationsException: Object name > >> cannot be null > >> > at > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > >> tered(Defa > >> ultM > >> >BeanServerInterceptor.java:545) > >> > at > >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > >> erver.java > >> :619 > >> >) > >> > at > >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis > >> try.java:6 > >> 42) > >> > at > >> >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > >> ocket.java > >> :706 > >> >) > >> > at > >> > >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) > >> > at > >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > >> (ThreadPoo > >> l.ja > >> >va:684) > >> > at java.lang.Thread.run(Thread.java:595) > >> >Caused by: java.lang.IllegalArgumentException: Object > name cannot be > >> null > >> > ... 7 more > >> >19-Nov-2004 10:43:47 org.apache.commons.modeler.Registry > >> >unregisterComponent > >> >SEVERE: Error unregistering mbean > >> >javax.management.RuntimeOperationsException: Object name > >> cannot be null > >> > at > >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > >> tered(Defa > >> ultM > >> >BeanServerInterceptor.java:545) > >> > at > >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > >> erver.java
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi, The next step, then, is to run a stress test in your test environment. See if you get the same errors. Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Allistair Crossley [mailto:[EMAIL PROTECTED] >Sent: Friday, November 19, 2004 8:45 AM >To: Tomcat Users List >Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 >mins. > >Hi Yoav, > >Tomcat standalone no. > >IIS > Tomcat > SQL Server > > Content Management System > >However, we have the same setup on test and production servers and test >does not exhibit this behaviour, perhaps due to load, or so on I expect. > >Cheers, Allistair > >> -Original Message- >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >> Sent: 19 November 2004 13:38 >> To: Tomcat Users List >> Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every >> 5-10 mins. >> >> >> >> Hi, >> I think I already know the answer to this, but I'll ask >> anyways: does it >> happen with Tomcat standalone? My guess is no. >> >> Yoav Shapira http://www.yoavshapira.com >> >> >> >-----Original Message----- >> >From: Allistair Crossley [mailto:[EMAIL PROTECTED] >> >Sent: Friday, November 19, 2004 6:32 AM >> >To: [EMAIL PROTECTED] >> >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 >> mins. >> > >> >Hi, >> > >> >Having run our web application on 5.5.4 for a couple of days, I have >> >studied the stdout logs to find that we are getting severe errors >> relating >> >to mbeans. Here are some time intervals: >> > >> >10:43 >> >11:10 >> >11:14 >> >11:24 >> > >> >This time pattern stays fairly consistent as above. >> > >> >Each time the errors occur, they appear as a set as follows below. >> > >> >Can I do anything to prevent this? >> > >> >Cheers, Allistair. >> > >> >SEVERE: Error unregistering mbean >> >javax.management.RuntimeOperationsException: Object name >> cannot be null >> >at >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis >> tered(Defa >> ultM >> >BeanServerInterceptor.java:545) >> >at >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS >> erver.java >> :619 >> >) >> >at >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis >> try.java:6 >> 42) >> >at >> >org.apache.jk.common.ChannelSocket.processConnection(ChannelS >> ocket.java >> :706 >> >) >> >at >> >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) >> >at >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >> (ThreadPoo >> l.ja >> >va:684) >> >at java.lang.Thread.run(Thread.java:595) >> >Caused by: java.lang.IllegalArgumentException: Object name cannot be >> null >> >... 7 more >> >19-Nov-2004 10:43:47 org.apache.commons.modeler.Registry >> >unregisterComponent >> >SEVERE: Error unregistering mbean >> >javax.management.RuntimeOperationsException: Object name >> cannot be null >> >at >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis >> tered(Defa >> ultM >> >BeanServerInterceptor.java:545) >> >at >> >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS >> erver.java >> :619 >> >) >> >at >> >org.apache.commons.modeler.Registry.unregisterComponent(Regis >> try.java:6 >> 42) >> >at >> >org.apache.jk.common.ChannelSocket.processConnection(ChannelS >> ocket.java >> :706 >> >) >> >at >> >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) >> >at >> >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >> (ThreadPoo >> l.ja >> >va:684) >> >at java.lang.Thread.run(Thread.java:595) >> >Caused by: java.lang.IllegalArgumentException: Object name cannot be >> null >> >... 7 more >> >19-Nov-2004 10:45:53 org.apache.commons.modeler.Registry >> >unregisterComponent >> >SEVERE: Error unregistering mbean >> >javax.management.RuntimeOperationsException: Object name >> cannot be null >> >at >> >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi Yoav, Tomcat standalone no. IIS > Tomcat > SQL Server > Content Management System However, we have the same setup on test and production servers and test does not exhibit this behaviour, perhaps due to load, or so on I expect. Cheers, Allistair > -Original Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 19 November 2004 13:38 > To: Tomcat Users List > Subject: RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every > 5-10 mins. > > > > Hi, > I think I already know the answer to this, but I'll ask > anyways: does it > happen with Tomcat standalone? My guess is no. > > Yoav Shapira http://www.yoavshapira.com > > > >-Original Message- > >From: Allistair Crossley [mailto:[EMAIL PROTECTED] > >Sent: Friday, November 19, 2004 6:32 AM > >To: [EMAIL PROTECTED] > >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 > mins. > > > >Hi, > > > >Having run our web application on 5.5.4 for a couple of days, I have > >studied the stdout logs to find that we are getting severe errors > relating > >to mbeans. Here are some time intervals: > > > >10:43 > >11:10 > >11:14 > >11:24 > > > >This time pattern stays fairly consistent as above. > > > >Each time the errors occur, they appear as a set as follows below. > > > >Can I do anything to prevent this? > > > >Cheers, Allistair. > > > >SEVERE: Error unregistering mbean > >javax.management.RuntimeOperationsException: Object name > cannot be null > > at > >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > tered(Defa > ultM > >BeanServerInterceptor.java:545) > > at > >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > erver.java > :619 > >) > > at > >org.apache.commons.modeler.Registry.unregisterComponent(Regis > try.java:6 > 42) > > at > >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > ocket.java > :706 > >) > > at > >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) > > at > >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > (ThreadPoo > l.ja > >va:684) > > at java.lang.Thread.run(Thread.java:595) > >Caused by: java.lang.IllegalArgumentException: Object name cannot be > null > > ... 7 more > >19-Nov-2004 10:43:47 org.apache.commons.modeler.Registry > >unregisterComponent > >SEVERE: Error unregistering mbean > >javax.management.RuntimeOperationsException: Object name > cannot be null > > at > >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > tered(Defa > ultM > >BeanServerInterceptor.java:545) > > at > >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > erver.java > :619 > >) > > at > >org.apache.commons.modeler.Registry.unregisterComponent(Regis > try.java:6 > 42) > > at > >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > ocket.java > :706 > >) > > at > >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) > > at > >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > (ThreadPoo > l.ja > >va:684) > > at java.lang.Thread.run(Thread.java:595) > >Caused by: java.lang.IllegalArgumentException: Object name cannot be > null > > ... 7 more > >19-Nov-2004 10:45:53 org.apache.commons.modeler.Registry > >unregisterComponent > >SEVERE: Error unregistering mbean > >javax.management.RuntimeOperationsException: Object name > cannot be null > > at > >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegis > tered(Defa > ultM > >BeanServerInterceptor.java:545) > > at > >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanS > erver.java > :619 > >) > > at > >org.apache.commons.modeler.Registry.unregisterComponent(Regis > try.java:6 > 42) > > at > >org.apache.jk.common.ChannelSocket.processConnection(ChannelS > ocket.java > :706 > >) > > at > >org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) > > at > >org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run > (ThreadPoo > l.ja > >va:684) > > at java.lang.Thread.run(Thread.java:595) > >Caused by: java.lang.IllegalArgumentException: Object name cannot be > null > > ... 7 more > >19-Nov-2004 10:45:54 org.apache.commons.modeler.Registry > >unregisterComponent
RE: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi, I think I already know the answer to this, but I'll ask anyways: does it happen with Tomcat standalone? My guess is no. Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Allistair Crossley [mailto:[EMAIL PROTECTED] >Sent: Friday, November 19, 2004 6:32 AM >To: [EMAIL PROTECTED] >Subject: 5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins. > >Hi, > >Having run our web application on 5.5.4 for a couple of days, I have >studied the stdout logs to find that we are getting severe errors relating >to mbeans. Here are some time intervals: > >10:43 >11:10 >11:14 >11:24 > >This time pattern stays fairly consistent as above. > >Each time the errors occur, they appear as a set as follows below. > >Can I do anything to prevent this? > >Cheers, Allistair. > >SEVERE: Error unregistering mbean >javax.management.RuntimeOperationsException: Object name cannot be null > at >com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(Defa ultM >BeanServerInterceptor.java:545) > at >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java :619 >) > at >org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:6 42) > 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(ThreadPoo l.ja >va:684) > at java.lang.Thread.run(Thread.java:595) >Caused by: java.lang.IllegalArgumentException: Object name cannot be null > ... 7 more >19-Nov-2004 10:43:47 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(Defa ultM >BeanServerInterceptor.java:545) > at >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java :619 >) > at >org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:6 42) > 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(ThreadPoo l.ja >va:684) > at java.lang.Thread.run(Thread.java:595) >Caused by: java.lang.IllegalArgumentException: Object name cannot be null > ... 7 more >19-Nov-2004 10:45:53 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(Defa ultM >BeanServerInterceptor.java:545) > at >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java :619 >) > at >org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:6 42) > 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(ThreadPoo l.ja >va:684) > at java.lang.Thread.run(Thread.java:595) >Caused by: java.lang.IllegalArgumentException: Object name cannot be null > ... 7 more >19-Nov-2004 10:45:54 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(Defa ultM >BeanServerInterceptor.java:545) > at >com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java :619 >) > at >org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:6 42) > 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(ThreadPoo l.ja >va:684) > at java.lang.Thread.run(Thread.java:595) >Caused by: java.lang.IllegalArgumentException: Object name cannot be null > ... 7 more >19-Nov-2004 10:51:02 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(Defa ultM >BeanServerI
5.5.4 SEVERE: Error unregistering mbean in stdout every 5-10 mins.
Hi, Having run our web application on 5.5.4 for a couple of days, I have studied the stdout logs to find that we are getting severe errors relating to mbeans. Here are some time intervals: 10:43 11:10 11:14 11:24 This time pattern stays fairly consistent as above. Each time the errors occur, they appear as a set as follows below. Can I do anything to prevent this? Cheers, Allistair. SEVERE: 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 19-Nov-2004 10:43:47 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: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 19-Nov-2004 10:45:53 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: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 19-Nov-2004 10:45:54 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: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 19-Nov-2004 10:51:02 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: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 19-Nov-2004 10:51:04 org.apache.commons.modeler.Registry unregisterComponent SEVERE: Error unregistering mbean javax.management.RuntimeOperationsException: Object name cannot be null at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistere
