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]