JK is known as "ajp13". JK2 is known as, I believe, "ajp14". The precursor
to JK was JServ, and that is known as "ajp12".
The Coyote Connector (org.apache.coyote.tomcat4.CoyoteConnector) can "speak"
JK and JK2. The Ajp13Connector (org.apache.ajp.tomcat4.Ajp13Connector) only
"speaks" JK.
CoyoteConnector: JK, JK2, SSL, HTTP
Ajp13Connector: JK
If you look in your server.xml, you will see
org.apache.coyote.tomcat4.CoyoteConnector used as ALL default connectors in
4.1.12, regardless of protocol.
>From what I understand (someone correct me if I am wrong), the administrator
app in 4.1.12 uses something call MBeans...Ajp13Connector has problems with
this. So, if you must use Ajp13Connector, comment out the MBeans tags in
server.xml, they look like this:
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
If you disable the mbeans Listeners, the administrator app will not work.
So, you basically have a choice:
CoyoteConnector: everything works, including the administration app
Ajp13Connector: JK only works, admin app doesn't
Some people are using Ajp13Connector because that's what they used in
previous versions of Tomcat, and some may feel that CoyoteConnector is still
untested. That's cool as long as they are using mod_jk and they don't mind
not having the administration app. If they want to use JK2 (mod_jk2) or
enable the administration app, then they need to use CoyoteConnector.
HTH
John
> -----Original Message-----
> From: John B. Moore [mailto:jbm@;microps.com]
> Sent: Friday, November 15, 2002 11:56 AM
> To: Tomcat Users List
> Subject: Re: non Http connector
>
>
> John,
>
> Maybe you can clear this up for me.. I get the hint from several
> different messages that the CoyoteConnector handles both JK and JK2.
> Looking at the server.xml it appears that, based on the comments in
> that file
>
> <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
> port="8009" minProcessors="5" maxProcessors="75"
> enableLookups="true" redirectPort="8443"
> acceptCount="10" debug="0" connectionTimeout="20000"
> useURIValidationHack="false"
>
> protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
>
>
> ...that the CoyoteConnector is ONLY for JK2 and that the
> "commented" tag
> below that:
>
> <!-- 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"/>
> -->
>
> ...is for JK.. Last I tried this, uncommenting this code
> threw errors..
>
> This Saturday I'm making another run at getting Apache2 and Tomcat4
> talking, and maybe clearing this up might help..<G>
>
> Thanks...
>
> John...
>
> Turner, John wrote:
>
> >Well, JK/JK2 are their own protocols, and the
> CoyoteConnector class handles
> >them just fine.
> >
>
>
> --
> 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>
