Struts is not the problem. Session replication was not set up correctly in WebSphere. IBM suggested a work around which is a setting in Websphere that changes the cookie name on a paticular appserver. You then end up with two session cookies. Thanks for the help.
The web server is the same. The domain is the same. The application server is different. We have Websphere which allows sessions to be shared across appservers. It works fine if I link to a servlet instead of struts.
Why does struts always create a new session? I have an application (non-struts) that creates a session. The user is then allowed to link to a struts application on another appserver. When the struts app comes up the existing session is blown away by struts. Why?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.