Troubleshooting: HTTP 410 errors and loss-of-session errors when in multinode cluster (WebSphere)
Symptom
Session affinity maintains a Process Commander user session to access one node in a clustered environment.
If you are using WebSphere 6.0.2 or 6.1 WebSphere Plug-In with Memory-to-Memory Session Management configured in a cluster, you may lose session affinity when a newly spawned web server process handles its first request.
When this occurs, a HTTP 410 message appears. This message text varies, it may be “Page Not Found” or “could not restore requestor”.
Solution
Explanation
This loss of session affinity occurs because the new process does not have a stored partition upon creation.
For more information on this issue see IBM article K48101: Newly spawned webserver processes break session affinity when memory-to-memory persistence is configured.
Resolution
To eliminate this issue, download and install the latest WebSphere Plug-in as follows:
- For WebSphere version 6.0.2 users, download 6.0.2.23.
- For WebSphere version 6.1 users, download 6.1.0.13.