You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ben Kimball <bk...@home.com> on 2001/08/23 01:30:37 UTC
Q: Is it possible to connect to Tomcat on NT from mod_jk on Solaris/Apache?
I have Tomcat running on NT. I have Apache running on Solaris. I am trying to
get mod_jk.so (on Solaris) to connect to Tomcat running on NT. (Not my idea -
work wants me to try to get this to work)
However, it seems that the workers.properties file needs to be seen by both
Tomcat itself and the mod_jk module, BUT the version of Tomcat on NT writes
out workers.properties using Windows-style directory names (Drive letters and
backslashes) which is meaningless to mod_jk on Solaris, as it does not grok
drive letters and expects forward-slashes.
First, I don't quite understand why mod_jk needs to know about
workers.properties - I would think it would just need to forward requests to
Tomcat and it would figure it out. (Or does it? When I leave out the Apache
directive for the location of the workers.properties file it refuses to
start, so I assume it does)
Secondly, what exactly in the workers.properties file does mod_jk need to
know? Can I perhaps point non-essential information to dummy directories (say
/dev/null or something) and translate only the needed information to
unix-directory format? Since once I get this going, it will only host this
one application and the configuration will never change, I was hoping I could
just do a one time translation to get the two to talk to each other.
Is there a way to do this, or is this just a silly thing to attempt?
Thanks!