Actually, I'm leaning towards a "bug" in mod_jk2 since a change in workers2.properties resulted in everything (so far) working. The only extra detail I had to add was explicit reference to index.jsp for both app's.
Did you have a chance to try the config change I suggested?
Robert
Joseph Shraibman wrote:
Robert Hall wrote:
Joseph,So the bug is in tomcat somewhere, not in mod_jk2?
We're using Apache 1.3.27 on solaris with mod_jk2 to connect to two JBoss/Tomcat instances
listening on separate ports. I experienced the same thing you described, all requests going to
one of the jk2 ports.
However, if I shutdown the JBoss/Tomcat instance that was getting all of requests, then the
other instance would start gettng the traffic. After restarting the "primary" instance I examined
jk2.log. It looked like the requests were heading to the correct server, but then would be "redirected"
to the primary.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
