The following table lists the known issues in the session replication functionality of Web Server 7.0.
Table 16 Known Issues in Session Replication
Problem ID |
Description |
---|---|
6370032 |
Session failover does not happen with RequestDispatcher include call. While deploying two web applications on a cluster where the first application calls on the second application using the RequestDispatcher() include call, the persistence valves are not called during the RequestDispatcher()'s invoke() method, and session replication does not occur. |
6381950 |
Incorrect load factor set for BaseCache. Session replication does not support more than two web applications. |
6381954 |
Session replication fails to work on multiple web applications involving RequestDispatcher due to bad sequence. |
6383313 |
Incorrect path is set on SR-intanceId cookie. The SR-instanceId cookie should be set to the web application's path instead of the servlet's path. |
6324321 |
Descriptive error message is not displayed when an error occurs remotely. When an exception occurs remotely, error messages are logged in the error log of the remote instance. However, the local instance currently displays a generic remote exception which does not clearly indicate which error log that the user must view. |
6396820 |
Session replication does not failover correctly when cookies are disabled on the client. |
6406176 |
When enabled, session replication should be the default session manager. After enabling session replication by using the Admin Console or the CLI, or by editing the server.xml file, session replication is not really enabled. Instead, sun-web.xml needs to be manually edited. |