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:[EMAIL PROTECTED]] > 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
