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

A failure occurred in the communication with the database.

Action

Make sure that the database is operating properly, no problem has occurred in the communication path between the database and J2EE server, and no mistakes exist in the change contents of the SQL file used for creating the table.

If an error 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 have been released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If the change contents of the SQL file used for creating the table are different from the settings of the application, either re-create the table to match the contents or change the settings of the application. For details on the procedure for changing the settings, see 6. Database Session Failover Functionality in the manual Cosminexus Application Server Function Guide - Expansion.

If no problem exists in the change contents of the database, communication path, and the SQL file used for creating the table, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.