uCosminexus Application Server, Expansion Guide
If you stop a web application or a J2EE server, or if a J2EE server becomes process down due to a failure, an HTTP session on the J2EE server is destroyed. The functionality that inherits global session information when restarting a web application is called Inhibiting global session information when starting a web application.
The following is the procedure of inheriting global session information when restarting a web application after a J2EE server is down due to a failure.
Note that global session information is not inherited in the case of the conditions described in the following table.
Table 5-11 Conditions and operations when global session information is not inherited
| No. | Condition | Operation |
|---|---|---|
| 1 | If you cannot obtain the list of session IDs of the global session information to be inherited from a database or an EADs server due to a network failure. | KDJE34345-W or KDJE34431-W# message is output to the message log and processing of inheriting the global session information ends. |
| 2 | If the global session information to be inherited already exists on the J2EE server (the information is already inherited on the J2EE server by receiving a request). | KDJE34347-I or KDJE34432-I message is output to the message log and processing of inheriting the global session information is skipped. |
| 3 | If the global session information to be inherited is already inherited on another replicated J2EE server by using the database session failover functionality. | KDJE34348-I message is output to the message log and processing of inheriting the global session information is skipped. |
| 4 | If you cannot obtain the global session information from a database or an EADs server due to a network failure. | KDJE34346-W or KDJE34434-W# message is output to the message log and processing of inheriting the global session information is skipped. |
| 5 | If you could not inherit because the number of HTTP sessions on the J2EE server reached the upper limit set by using the functionality of specifying the upper limit of number of HttpSession objects. | KDJE34370-W or KDJE34435-W# message is output to the message log and processing of inheriting the global session information is skipped. |
| 6 | If deserialization of the global session information fails. | KDJE34328-E or KDJE34436-E message is output to the message log and global session information is not inherited and deleted from the database or the EADs server. |
| 7 | If you are using the database session failover functionality and you change the server ID set by the functionality of adding server ID of HttpSession. | KDJE34348-I message is output to the message log and processing of inheriting the global session information is skipped. |
# If this message is output, again start the web application by eliminating the cause of the failure or the global session information continues to remain in the session information cache on the EADs server until a request is received and inherited. For details on the procedure of deleting remaining global session information, see 7.8.1 Deleting global session information on an EADs server (session information storage destination server).
All Rights Reserved. Copyright (C) 2013, 2015, Hitachi, Ltd.