In the default 4.1.x server.xml file there is an un-commented out entry: <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8009" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" useURIValidationHack="false" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" />
This is the "coyote connector". Use this one instead of the AjpConnector if you want to enable the "admin" webapp that has the very nice GUI to allow you to configure your server. If you don't care about this, remove (or comment out) the two lines under <Server> that have <Listener className="org.apache.catalina.mbeans...." />. In this case, the "admin" application won't work, but you can use the legacy AjpConnector. "Anderson, M. Paul" <[EMAIL PROTECTED]> wrote in message news:D66093F40B7B4B428A20AD9796835FD17FE442@;central.ssd.jhuapl.edu... > 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:hoju@;visi.com] > 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:tomcat-user-unsubscribe@;jakarta.apache.org> > AMP> For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> > > > > -- > Best regards, > Jacob mailto:hoju@;visi.com > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
