Hello - There's no need for jk2.properties with mod_jk. The connector used on the Tomcat side doesn't affect the configuration needed for the Apache module. If you are using mod_jk and not mod_jk2, the only configuration file you need is workers.properties, and that is regardless of using Ajp13Connector or CoyoteConnector on the Tomcat side. CoyoteConnector can handle HTTP, HTTPS, JK, and JK2.
John > -----Original Message----- > From: Pedro Salazar [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 16, 2003 11:50 AM > To: Tomcat Users List > Subject: configure CoyoteConnector with mod_jk in tomcat 4.1.x > > > Greetings, > > I would like to use the CoyoteConnector rather than the Ajp13Connector > since I'm using tomcat 4.1(.17) and the listener > org.apache.catalina.mbeans.GlobalResourcesLifecycleListener (to have a > global database resource) is incompatible with Ajp13Connector > (plus the > Ajp13Connector will be deprecated facing the CoyoteConnector). > > But I don't know how to configure the jk2.properties of the > CoyoteConnector for tomcat. I have in my apache server pointing to a > older worker.properties (simple configuration) that should > work with the > jk2.properties - I believe that for both of them are required (one for > apache and one for tomcat). > > How should I define the workers list in jk2.properties for they match > with the workers.properties of apache? > > For now I didn't touch in jk2.properties (is all commented). > And I have > defined a worker called ajp13 (type ajp13) in the > workers.properties for > apache. > > My configuration is: > -apache2.0.43 + mod_jk > -tomcat 4.1.17 > -linux redhat 8.0 (2.4.19) > > thanks, > Pedro Salazar > > > -- > 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]>
