The Ajp13Connector isn't supported for the manager webapp in 4.1.x. You have to use the CoyoteConnector if you want to connect Tomcat to IIS and also use the manager webapp. The entry in server.xml looks like:
<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" /> ----- Original Message ----- From: "Isabel Lameda" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <[EMAIL PROTECTED]> Sent: Tuesday, August 13, 2002 11:48 AM Subject: RE: Tomcat 4.1 in production I�m having a problem with Tomcat 4.1.8 Beta. I�ve set up all i need to view jsp files in IIS and the problem is that when when i uncomment the line for the ajp 1.3 Connector in the server.xml, which is: <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" port="8009" minProcessors="5" maxProcessors="75" acceptCount="10" debug="0"/> I get this exception: INFO: Creating MBeanServer 12/08/2002 04:22:10 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:359) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:716) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:690) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:329) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2181) at org.apache.catalina.startup.Catalina.start(Catalina.java:510) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) 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.catalina.startup.Bootstrap.main(Bootstrap.java:203) Starting service Tomcat-Standalone Apache Tomcat/4.1.8 12/08/2002 11:26:32 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Every thing works fine, except that i cannot use the Administration Tool, when i open it i get this: HTTP Status 503 - Servlet action is currently unavailable type: Status report message: Servlet action is currently unavailable description: The requested service (Servlet action is currently unavailable) is not currently available. If i comment back the line for the ajp connector the administration tool works fine but the thing is that i need to use the connector. I'm also worry about what other problems could involve that exception, because until now i�ve only found that with the administration tool. In the server.xml i also have this lines referencing some listeners: <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" debug="0"/> <ListenerclassName="org.apache.catalina.mbeans.GlobalResourcesLifecycleListe ner"debug="0"/> If i comment the first one, the exception disapeers and every thing works but i cannot either use the administration tool Regards -----Mensaje original----- De: Wills, Mike N. (TC) [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 02:26 p.m. Para: 'Tomcat Users List' Asunto: Tomcat 4.1 in production I have heard of some people using Tomcat 4.1 in a production environment. I know that running beta software is usually a bad thing. What are people's experiences with it here? Mike Wills -- 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]>
