Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 85241 invoked from network); 15 Oct 2002 16:20:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Oct 2002 16:20:09 -0000 Received: (qmail 15793 invoked by uid 97); 15 Oct 2002 16:20:33 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 15625 invoked by uid 97); 15 Oct 2002 16:20:32 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 15539 invoked by uid 98); 15 Oct 2002 16:20:31 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Date: Tue, 15 Oct 2002 10:19:38 -0600 From: "Jeff Tulley" To: Subject: Re: MBeanException w/AJP13Connector and (hopefully) itssolution Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N So I find that works on NetWare with our mod_jk, as you said. The only = thing that worries me is that the port value set in server.xml is not = honored, on Windows or on NetWare. Is there somewhere else it is pulling = its configuration from? I cannot have shifting ajp ports, since I might = have two catalina instances running simultaneously, and I need to control = what port Apache sends requests to, so that I can route them right. What I saw was that I set the port to 9010, but Catalina still comes up = with "ajp13 listening on tcp port 8009". When I fire up the second = instance of Catalina, it comes up listening on 8010, after unsuccessfully = trying to get port 8009. I cannot just use 8009 and 8010, due to both = port conflicts on NetWare(with 8009), and because I do not want to rely on = startup order of the two Catalina instances. Is this a bug, or is there some part of the design that I'm missing? Jeff Tulley (jtulley@novell.com) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> JTULLEY@novell.com 10/15/02 9:44:57 AM >>> So I'm barking up the wrong tree? I thought somebody had told me that the = Coyote JK 2 connector only worked with mod_jk2. I'll go play around with = the Coyote / mod_jk combo on NetWare, and see how it works. Thanks. Jeff Tulley (jtulley@novell.com) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com=20 >>> remm@apache.org 10/15/02 1:08:06 AM >>> Jeff Tulley wrote: > When I uncomment the AJP13 Connector, I get the following exception on = startup: > ServerLifecycleListener: createMBeans: MBeanException = =20 > java.lang.Exception: ManagedBean is not found with Ajp13Connector = =20 > at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.j= ava:225) = =20 > at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean= s(ServerLifecycleListener.java:369) = =20 > at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean= s(ServerLifecycleListener.java:777) = =20 > at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean= s(ServerLifecycleListener.java:751) = =20 > at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean= s(ServerLifecycleListener.java:339) = =20 > at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEv= ent(ServerLifecycleListener.java:206) = =20 > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L= ifecycleSupport.java:166) = =20 > at org.apache.catalina.core.StandardServer.start(StandardServer.j= ava:2182) = =20 > at org.apache.catalina.startup.Catalina.start(Catalina.java:510) = =20 > at org.apache.catalina.startup.Catalina.execute(Catalina.java:400= ) =20 > at org.apache.catalina.startup.Catalina.process(Catalina.java:180= ) =20 > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) = =20 > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess= orImpl.java:39) = =20 > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth= odAccessorImpl.java:25) = =20 > at java.lang.reflect.Method.invoke(Method.java:324) = =20 > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)= =20 >=20 > I'm wondering if the fix is simply to add a section into catalina/src/sha= re/o/a/c/mbeans/mbeans-descriptors.xml, describing the AJP 13 connector? >=20 > I've attached my naive fix to this, which is to copy the Coyote = connector section, removing only the protocolHandler attribute, since that = is unique to Coyote(if I'm not mistaken, I very well could be). >=20 > Could I get one of the committers to review this please and submit the = change? We need this for NetWare, which does not have a port of mod_jk2 = yet. Either Coyote JK 2 or the old AJP 1.3 connector can be used with mod_jk=20 (that's why the AJP 1.3 connector is deprecated). Remy -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: