Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <83F0258A9996D311B14200A0C98F173602F22B64@aas-internet.aas.com>
From: "Turner, John" <JTurner@AAS.com>
To: 'Tomcat Users List' <tomcat-user@jakarta.apache.org>
Subject: RE: mod_jk tomcat/apache connector issue
Date: Tue, 7 Jan 2003 14:45:22 -0500 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"


Well, CoyoteConnector can support multiple protocols: JK, JK2, HTTP, HTTPS,
depending on how it's used, what port it is listening on, etc.
CoyoteConnector is enabled by default on port 8009 in Tomcat 4.1.x for
JK/JK2.  If you disable that connector and enable Ajp13Connector (disabled
by default in Tomcat 4.1.x) on port 8009 instead, you can only use JK.  

Note that the ApacheConfig auto-gen feature for JK is distinct from the
connector class you are using for JK.  You can use ApacheConfig with
CoyoteConnector, as long as you use mod_jk and not mod_jk2 on the Apache
side.

John


> -----Original Message-----
> From: adrian [mailto:adrianthiele@netzero.net]
> Sent: Tuesday, January 07, 2003 1:27 PM
> To: Tomcat Users List
> Subject: Re: mod_jk tomcat/apache connector issue
> 
> 
> One more idea, look at mod_jk.conf, I had the same error last night.
> Line 4 dictates where mod_jk.so is located. I ran apachectl configtest
> and it told me that mod_jk was not located at /etc/httpd/libexec/
> I included the modJk=/usr/lib/apache/mod_jk.so , but it didn`t
> work until I put mod_jk.so where it was looking.
> Line 4 is the include for mod_jk.so.
> Sounds like the same problem.
> I was wrong about the connector, John said last night the JK2 
> connectors
> backwards compatable with jk.
> 

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>