We do not send cookies. Our clients are not web pages but applications embedded in proprietary hardware, which connect to our network via landline telephone or cell modem and access our servlet via HTTP connection. The servlet responds by sending a message containing several parameters in name-value pair format, including a session id that appears as: "session-id= <unique_client_identifier>-<current_time_in_milliseconds>". The client will respond to the servlet with a message that contains the same session id name-value pair. After initial connection, all client-server communications will contain this unique session id name-value pair.
Apache will forward the requests/responses as expected when a single Tomcat node is running. However, for multiple nodes, the requests are forwarded round robin to all nodes. Our system environment prevents us from using session replication between nodes, so we have to use sticky sessions. I do not believe the problem is with Tomcat, but rather how mod_jk routes the requests. Is there any way to configure mod_jk so that it will recognize the session id name-value pair? -----Original Message----- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Friday, July 15, 2011 9:44 AM To: users@tomcat.apache.org Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8 On 15.07.2011 12:48, Lataxes, Karl wrote: > 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? How does the client present the session id as part of the requests? Query parameter, path info, request header, cookie, ...? Can you five a complete example? Regards, Rainer --------------------------------------------------------------------- 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
