[TechNote] JSESSIONID information lost when navigating across servers

JSESSIONID information lost when navigating across servers

Problem(Abstract)

When a IBM® WebSphere® Application Server client user navigates across applications running in multiple Application Servers in the same domain, then cookie information might get overwritten causing session loss.

Cause

JSESSIONID value generated by one Application Server might not be known to other server and cookie information will be over-written.

Resolving the problem

To fix this problem, rename the JSESSIONID cookie name from WebSphere Application Server administrative console:

For WebSphere Application Server V6.1, V7 and V8:

1. Open the administrative console.
   
2. Go to Servers > Application Servers > Server_Name > Web Container Settings > Session management > Enable Cookies
   
3. Change the value for session cookie name.
   
4. Click OK.
   
5. Save changes.
   
6. Restart Application Server
   
7. Regenerate plug-in configuration file.
   
8. If running remotely, copy plug-in to remote server.