|
Problem |
WebSphere Application Server will use the JSESSIONID
information to keep track of the client session.
If you have an application, where application client has to navigate
across multiple WebSphere Spplication Server nodes residing in same
domain, then JSESSIONID information might get over written at client,
because of multiple JSESSIONID cookies received with same name and
path. |
|
Cause |
When persistence is not enabled and if the JSESSIONID that
came in incoming request is not found in current session manager, then
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 application client navigates across
servers. |
|
Solution |
To overcome the above problem, you can configure WebSphere
Application Server to reuse the sessionId present in the incoming request.
For V6.0:
- Open 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 JVM to reuse the sessionId:
System Property Name: HttpSessionIdReuse
System Property Value: true
- Save changes and restart the Application Server.
For V5.0 or V5.1:
- Open administrative console,
- Select Servers > Application Servers > Server_Name
> JVM Settings > System Property > New
- Add a new Custom Property for JVM to reuse the sessionId:
System Property Name: HttpSessionIdReuse
System Property Value: true
- Save changes and restart the Application Server.
For V4.0:
- Open administrative console,
- Select Nodes > Servers > Server_Name
> JVM Settings > System Properties > Add
- Add a new Custom Property for JVM to reuse the sessionId:
System Property Name: HttpSessionIdReuse
System Property Value: true
- Save changes and restart the Application Server.
|
|
|
|
|
|
|