Great - no more messing with damn mod_jk2. Relief! Thanks
John -----Original Message----- From: John Turner [mailto:[EMAIL PROTECTED] Sent: 14 August 2003 15:03 To: Tomcat Users List Subject: Re: Problem with mod_jk and admin application in Tomcat 4.1 I didn't mean mod_jk2. I meant CoyoteConnector in server.xml. In server.xml, you have a connector listening on some port (like 8009) for communications from Apache. This connector has a class parameter. In your case, the class is "org.apache.ajp.tomcat4.Ajp13Connector". Make it "org.apache.coyote.tomcat4.CoyoteConnector" instead and you will be able to use MBeans. CoyoteConnector can handle AJP13 from either mod_jk or mod_jk2, as well as HTTP and HTTPS. There are actually two Apache connectors in server.xml by default, one uses Ajp13Connector, one uses CoyoteConnector: <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --> <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"/> <!-- Define an AJP 1.3 Connector on port 8009 --> <!-- <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" port="8009" minProcessors="5" maxProcessors="75" acceptCount="10" debug="0"/> --> You want the first one, not the second one. John J.P. Wadkin C9951627 wrote: > I would use JK2 if it worked on Solaris 8 with Apache 2, which it > doesn't - or at least I haven't been able to get it to work and I've > tried everything. > > > John > > -----Original Message----- > From: John Turner [mailto:[EMAIL PROTECTED] > Sent: 14 August 2003 14:43 > To: Tomcat Users List > Subject: Re: Problem with mod_jk and admin application in Tomcat 4.1 > > > > You're using a sledgehammer where a light tap will do fine. > > Ajp13Connector doesn't like MBeans, or vice versa. > > Either don't use MBeans, or use CoyoteConnector instead of > Ajp13Connector. The latter is preferred and recommended, Ajp13Connector > > is deprecated. > > John > > J.P. Wadkin C9951627 wrote: > > >>It seems that it's not possible to use mod_jk with the admin > > application > >>in Tomcat 4.1 >> >>On startup this appears in catalina.out >> >>ServerLifecycleListener: Creating MBean for Service >>StandardService[Tomcat-JK] >>ServerLifecycleListener: Creating MBean for Connector >>[EMAIL PROTECTED] >>ServerLifecycleListener: createMBeans: MBeanException >>java.lang.Exception: ManagedBean is not found with Ajp13Connector >> <stack trace> >> >>So I edited the mbeans-descriptors.xml file in the catalina.jar and >>added an mbean for the Ajp13Connector. Tomcat started fine (no errors) >>but mod_jk no longer works - any request to a webapp URL results in a >>404 error. There's nothing in the logs - just the 404 errors. I'm not >>sure why this is - there's a mbean for the Coyote/jk2 connector so >>presumably this works? >> >> >>Thanks >> >>John >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
