Our servlet assigns a session id to a client when it initially contacts the server. The session id consists of "session-id", a unique client identifier, and the current time in milliseconds, which is used as session identification for subsequent requests. There are numerous message exchanges between the servlet and client during a typical session, all of which contain the session id. Once the session has successfully ended, the session id is removed from the servlet.
Is there any way we can configure mod_jk to recognize the session id in order to route subsequent messages to the original Tomcat node it initially contacted? -----Original Message----- From: Mark Thomas [mailto:ma...@apache.org] Sent: Wednesday, July 13, 2011 3:12 PM To: Tomcat Users List Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8 On 13/07/2011 19:39, Lataxes, Karl wrote: > We're not using cookies. > > Our application is not web based, but accepts HTTP PUTS via client requests > that enter our network from external sources. We are not URL encoding, as > our clients are not configured to accept it. If we have to include URL > encoding, both our client and server applications will have to be modified > accordingly, which may be an option. No cookies and no url encoding. OK. So how are requests associated with a session? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
