JK - warning/question about naming workers

["Madere, Colin" <co...@ieminc.com>]

I just fought with a problem for quite a while and thought I'd share a
caution and ask a question.

The mod_jk.conf auto-generated by Tomcat assumes that your worker for the
/examples (and other default apps in Tomcat) is named "ajp13".  If you name
it anything else you'll get a 500 error since JK drops the request due to no
valid worker being found.  You MUST name a worker "ajp13" for those things
to work.

This brings up a question for me, how does Tomcat decide to map apps to
workers to auto-generate mod_jk.conf correctly?  Does it assume that you
will have all contexts that you want to map to a worker under a single host?
If so, doesn't this imply that you can't map multiple workers to the same
host (if Tomcat keys off the host)?  Am I off in left-field?  In all the
documentation I've sought out did I miss the explanation of this somewhere?

Thanks again to those vigilant responders on this list!

Colin


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>