Loss of persisted sessions in WebSphere Application Server when requests alternate between clones running compliance and compatibility mode

Technote (FAQ)
Problem
One of the differences when moving from compatibility mode (servlet 2.1 specification) to compliance mode (servlet 2.2 specification) is that sessions cannot be shared across Web applications. A problem arises if clones were created in WebSphere Application Server prior to installing Fix Pack 4. Web applications of these clones are named by the original Web application name followed by Clone.

This creates a Web application with a different name that, when in compliance mode, is considered a different application. As a result, the Web application is not allowed to share session data. A review of the XMLConfig -export for the Web application names on each clone can confirm this naming issue.
Solution
Do one of the following:
  1. Rename the cloned Web applications through the administrative console by highlighting the Web application on the clones and changing the name in the right hand panel. Click Apply.

    or

  2. Delete the clones and recreate them on WebSphere Application Server 3.5.4 or higher that has corrected this naming issue. The cloned Web applications have the same name as the original and are not considered two different applications. The sessions are retrieved correctly.











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Sessions and Session Management
Operating system(s): Multi-Platform
Software version: 3.5.3, 3.5.4, 3.5.5, 3.5.6
Software edition: Edition Independent
Reference #: 1054827
IBM Group: Software Group
Modified date: 2004-09-07