Transfer of global sessions at Web application startup failed because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, DB Connector = dd....dd, exception = ee....ee)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: HTTP session ID that could not be inherited
dd....dd: Optional name of the DB Connector
ee....ee: Information about the exception that occurred

Description

The global session information could not be inherited during the startup of the Web application because a failure occurred during database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not be released. Before restarting the business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, make sure that the settings of the connection timeout of the DB Connector are correct.

If the settings of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).