That was exactly it! Thank you. I had changed the configs, but had not commented in that section. All is well now. Thank you very much!
|)ave -----Original Message----- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 05, 2005 6:51 PM To: Tomcat Users List Subject: Re: Authentication problems with tomcat clustering. On Apr 5, 2005 3:13 PM, David Owens <[EMAIL PROTECTED]> wrote: > After further debug, I see this is happening because mod_jk is > "ignoring" the sticky sessions, and continuing to lb back and forth. > After looking at the mod_jk code, I see it is looking for something > after the '.' character in the JSESSIONID to tell it where the session > should stick. > > How do I setup tomcat (or is it httpd) to provide this piece of > information? The name of your worker in the mod_jk config must match the value in each Tomcat instance's server.xml. For example (abbreviated configs) in tomcat-workers.properties: worker.list=tomcat1,tomcat2 And in tomcat1's server.xml: <Engine jvmRoute="tomcat1"/> And in tomcat2's server.xml: <Engine jvmRoute="tomcat2"/> Hope this helps... -Dave --------------------------------------------------------------------- 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]
