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]

Reply via email to