|
Problem(Abstract) |
IBM® WebSphere® Application Server uses the JSESSIONID
information to keep track of the client session. If you have an
application where the application client must navigate across multiple
WebSphere Application Server nodes residing in same domain, then the
JSESSIONID information may be over-written on the client because multiple
JSESSIONID cookies received with the same name and path. |
|
|
|
Cause |
When persistence is disabled and if the JSESSIONID in the
incoming request is not found in the current session manager, then the
session manager will generate a new sessionId and create a session object,
instead of using the sessionId in the incoming request. This would cause
problems with session data when the application client navigates across
servers. |
|
|
Resolving the
problem |
To resolve this issue, configure WebSphere Application
Server to reuse the sessionId present in the incoming request.
For V6.0
- Open the administrative console.
- Select Servers > Application Servers > Server_Name
> Server Infrastructure > Java and Process Management >
Process Definition > Java Virtual Machine > Custom Properties >
New.
- Add a new Custom Property for the JVM to reuse the sessionId:
System Property Name: HttpSessionIdReuse
System Property Value: true
- Save your changes and restart the Application Server.
For V5.0 or V5.1
- Open the administrative console.
- Select Servers > Application Servers > Server_Name
> Process Definition > Java Virtual Machine > Custom
Properties > New.
- Add a new Custom Property for the JVM to reuse the sessionId:
System Property Name: HttpSessionIdReuse
System Property Value: true
- Save your changes and restart the Application Server.
|
|
|