Never mind.  I think I figured it out.  In mod_jk.conf you have a
JkWorkersFile path/to/worker.properties
 
and in worker.properties you specify the ports your workers are listening on.  So mod_jk.so is probably able to read this in.
-----Original Message-----
From: Amjad Ashraf [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 9:21 PM
To: '[EMAIL PROTECTED]'
Subject: how does mod_jk know which port to send to

Hey,
 
how does mod_jk know which port tomcats workers (aj12, aj13) are listening on?  I mean, when httpd starts it reads mod_jk.conf which tells it how to configure mod_jk.so and how to use it, but there is no mention of port.  But I noticed that when using mod_jserv.so that in mod_jserv.conf (or tomcat-apache.conf) there is a ApJServDefaultPort 8007 directive telling mod_jserv.so which port the worker is listening on.  Shouldn't there be a port directive for mod_jk?
 
I'm just trying to figure out why my mod_jk configuration doesn't work.  I'm getting plain text served up when I hit jsp's through apace.

Reply via email to