uCosminexus Application Server, Messages
![[Contents]](FIGURE/CONTENT.GIF)
![[Back]](FIGURE/FRONT.GIF)
KDJE34377-E
An attempt to clear the global sessions failed because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)
- aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Optional name of the DB Connector
dd....dd: Information about the exception that occurred
- Description
- An attempt to delete the global session information or the global session information whose valid period has expired failed because a failure occurred in the 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, the exclusion in the database might not be released. Check the invalid connections and release the unreleased exclusion.
- If no problem exists in the database and communication path, make sure that the setting of the connection timeout of the DB Connector is correct. If the setting 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).
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.