5.7.2 Inheriting global session information when starting a web application

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.

Obtain the list of session IDs of the global session information to be inherited from a database.

Obtain the list of session IDs of the global session information to be inherited from a database when starting a web application.
Execute the processing of inheriting the global session information.

When you obtain the list of session IDs, output KDJE34344-I or KDJE34429-I message to the message log and start the processing of inheriting global session information.

With processing of inheriting the global session information, inherit the global session information of the session IDs included in the list one by one from the database to the J2EE server.

If you cannot inherit the global session information, a message corresponding to the cause of the failure is output.
End the processing of inheriting.

When the processing of inheriting all global session information present in the list of session IDs completes, KDJE34349-I or KDJE34430-I message is output to the message log.

Note that global session information is not inherited in the case of the conditions described in the following table.

Table 5‒6: 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 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 due to a network failure.	`KDJE34346-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` 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.
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.

To Page Top