So JK (mod_jk) is incompatible with Tomcat 4.1.10? Or is there a configuration parameter that turns off the JMX features?
John > -----Original Message----- > From: Remy Maucherat [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 09, 2002 4:09 PM > To: Tomcat Users List > Subject: Re: AJP 1.3 Connector fails to load on Tomcat 4.1.10 > > > Giorgio Ponza wrote: > > Hi all. > > I need to connect Apache 2.0.40 with Tomcat 4.1.10 and mod_jk.so > > Following the instruction given by John Turner, i uncomment > this line in > > server.xml > > but i get an error (later in this mail) > > > > I tried with Tomcat 4.1.10 LE J2SE 1.4.0 and with the full > installation, but > > with the same results. > > Also the libraries are the same for the 2 versions. > > > > Any help is welcome. > > Giorgio > > > > <!-- 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"/> > > --> > > > > > > > The problem is that you can't use the old AJP connector with the JMX > features. > > Either: > - remove the ServerLifecycleListener (at the beginning of server.xml) > - use JK2 for AJP 1.3 support (it's a lot faster also) > > Remy > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
