Yeah, his response didn't make total sense. By default, everything in Tomcat Catalina should have a MBean equivalent that you shouldn't have to worry about as a user. It is something "under the covers" to make management of tomcat (the /admin app) work better. It is just that, when somebody went to define the MBean resources in an XML file in the source code, they skipped the AJP13Connector since it is considered "deprecated". If I am not mistaken, the problem caused by this exception is that the admin app doesn't always function correctly. Sometimes it simply comes up with a "page not found" and I think this exception might be the problem. Shutdown is also problematic because the JMX stuff isn't fully set up right.
The default server.xml (Tomcat 4.1.7 and higher, I think, 4.1.12 for sure) should use the Coyote connector JkHandler by default, and the AJP13Connector should be commented out. I know this to be the case because on NetWare we had to explicitly switch that around to use the AJP13Connector. I think in the future we are also going to move to using the defaults, just keeping the Coyote Connector. Are you adverse to fixing up your tomcat instance? I can send the patch that I have - to jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/mbeans-descriptors.xml This adds in a section that describes the AJP13Connector, getting rid of the immediate problem. You would have to then replace the mbeans-descriptors.xml file in server\lib\catalina.jar with your patched one (with the right path, org\apache\catalina\mbeans). That fixed the problem for us, though long term I'd move away from this connector. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] 11/14/02 2:33:14 PM >>> What do you mean "set up your configuration with the coyote connector"? I followed the documenation as given and it uses the AjpConnector. What is it that is using MBeans? I'm totally confused! I am completely new to tomcat and apache and would appreciate any clarification! How can I comment out the MBeans that are causing the exception? Will this exception cause instability or can I just ignore it without fear of further problems? Please Help!!! I've looked at the default server.xml and I don't see any help there. -----Original Message----- From: Jacob Kjome [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 14, 2002 3:20 PM To: Tomcat Users List Subject: Re: ManagedBean is not found with Ajp13Connector Hello M., The Ajp13Connector doesn't support MBeans. You need to set up your AJP configuration with the CoyoteConnector instead. Or, just comment out the MBeans that are causing the exception. See Tomcat-4.1.12's default server.xml for reference. Jake Thursday, November 14, 2002, 2:12:41 PM, you wrote: AMP> I have just completed setting up the Apache 1.3.27 web server which will be AMP> used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using AMP> j2sdk1.4.0_02. I have set up the configuration of my server.xml and AMP> https.conf files as described in the tomcat online help for the AMP> ajp13Connector. When I run them, however, I get an exception stack that AMP> looks like this (this is from my stdout.log file): AMP> Bootstrap: Create Catalina server AMP> Bootstrap: Starting service AMP> ServerLifecycleListener: createMBeans: MBeanException AMP> java.lang.Exception: ManagedBean is not found with Ajp13Connector AMP> at AMP> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:369) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:777) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:751) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:339) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife AMP> cycleListener.java:206) AMP> at AMP> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor AMP> t.java:166) AMP> at AMP> org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) AMP> at AMP> org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) AMP> at java.lang.reflect.Method.invoke(Native Method) AMP> at AMP> org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 AMP> ) AMP> at AMP> org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) AMP> Starting service Tomcat-Standalone AMP> Apache Tomcat/4.1.12 AMP> The server works fine and I can invoke my servlets and jsp pages through AMP> apache without a problem. My question concerns this error. I have searched AMP> the net to find an answer but I can't find what this problem is. I am AMP> satisfied that I have configured the servers properly since I can view my AMP> pages but I need to know what that error is so I can be satisfied it won't AMP> cause any future problems. AMP> Any help would be greatly appreciated!! AMP> Paul AMP> -- AMP> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> AMP> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Best regards, Jacob mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
mbeans-descriptors.patch
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
