Regarding Sticky Session

[Sachin Dare]

Hello World,

Currently I am working on one system. In development we are using Tomcat server. But in production we are using Apache as a load balancer and Tomcat as web server. Our Architecture has a problem of "Sticky Session" i.e. the request of particular user always goes to particular server. I have some questions in my mind -

1. Does the sticky sessions are always harmful? If not what is the scenario when we require having sticky sessions.

2. To avoid the sticky session we are planning to shift session management on Apache. Does this require any code changes or will it be just a configuration change?
It will be great if anyone can explain me the process of shifting session management from Tomcat to Apache.

Thanks a lot for your kind suggestions in advance.
Thanks and Regards,
Sachin Dare.

[Winston Gutkowski]

Sachin Dare wrote:It will be great if anyone can explain me the process of shifting session management from Tomcat to Apache.

Fraid I can't help much on your particular problem, but it doesn't seem like a good idea to have different setups for your development and production. At the very least you should have a test area that mimics your prod environment as closely as possible; usually pretty simple in these days of partitioned OS's.

Winston

[Jeanne Boyarsky]

Closing because a duplicate of this question in servlets