I get the MBean exception but still have Apache / Tomcat connectivity via the 
AJP13Connector.

It is probably not related.  You might try using the Coyote Jk Handler, since it is 
compatible with mod_jk (we had not realized that the two would work together, and that 
was the only reason to move on).  I mention this option because maybe you'd have more 
luck with the other connector talking ot mod_jk, or just a different set of problems.  
:)

Oh, if you do go this route, get the absolute latest CVS code, since Costin recently 
made some crucial changes that make the Coyote JK Handler use the port values set in 
server.xml.

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com

>>> [EMAIL PROTECTED] 11/5/02 12:00:13 PM >>>
Folks,

OK, I hate to do this, but I've searched the archives and monitored  
this list for a few weeks now, and I still can't get this to work. I  
want to set up Apache and Tomcat on my G4 Mac with OSX 10.2.1 for  
development (I want to eventually have the same set up on my production  
RedHat machine, which is currently running Apache1.3.12/Tomcat3.3.1  
with mod_jk). Anyway, I've followed John Turner's Howto for the most  
part. I have installed Apache 2.0.43, Tomcat 4.1.12, and mod_jk. I have  
modified server.xml, workers.properties, and httpd.conf per John  
Turner's Howto and the docs, and they just won't talk to each other.  
And, when I start Tomcat, I get this in catalina.out:

[INFO] Registry - -Loading registry information
[INFO] Registry - -Creating new Registry instance
[INFO] Registry - -Creating MBeanServer
[INFO] Http11Protocol - -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(ServerLi 
fecycleListener.java:369)
        at  
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi 
fecycleListener.java:777)
        at  
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi 
fecycleListener.java:751)
        at  
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi 
fecycleListener.java:339)
        at  
org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(Server 
LifecycleListener.java:206)
        at  
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu 
pport.java:166)
        at  
org.apache.catalina.core.StandardServer.start(StandardServer.java:2182)
        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 java.lang.reflect.Method.invoke(Native Method)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080

I don't know if that's a related problem or not, but I also searched  
the archives on this and couldn't find the problem. I even tried  
commenting out the JMX MBeans portion of server.xml, thinking maybe it  
wasn't compatible with ajp13, but that didn't help (it did get rid of  
the excepyion).

Apache works fine on port 80 and Tomact works fine on port 8080. Let me  
know if you want me to post more of the config files, and feel free to  
respond privately or to the list.

Thanks!

Mark

--
Mark L. Diana, MBA
Instructor
LAN Manager & Webmaster
Virginia Commonwealth University
Department of Health Administration


--
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>

Reply via email to