Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: HTTP 410 errors and loss-of-session errors when in multinode cluster (WebSphere)

Updated on May 7, 2019



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”.




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 WWWK48101: Newly spawned webserver processes break session affinity when memory-to-memory persistence is configured.


To eliminate this issue, download and install the latest WebSphere Plug-in as follows:


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us