Connection retry is a functionality that automatically retries to obtain a connection when there are no available connections in the connection pool and when the establishment of a physical connection fails. By using the connection retry functionality, if an attempt to obtain a connection fails, you need not use the user program to retry to obtain a connection.
You can retry to obtain a connection when one of the following conditions is satisfied:
Note that if a connection cannot be obtained even after retrying, an exception is reported to the application program and the process of obtaining a connection fails.
For the operations to be performed when the connection pool depletes, follow the description in 3.15.2 Waiting for a connection when connections deplete.
To implement the connection retry functionality, you must set up the following content as the resource adapter properties:
Note that if the retry count and retry interval is increased, the requests might have to wait when the processing to obtain connections accumulate.
For details on the resource adapter settings, see 3.15.13 Settings in the execution environment.
The following table describes the preconditions for using the connection retry functionality.
Table 3-58 Using the connection retry functionality
Resource | Connection method | Usability |
---|---|---|
Database | DB Connector | Y |
Database queue | DB Connector for Cosminexus RM and Cosminexus RM | Y |
OpenTP1 | uCosminexus TP1 Connector | Y |
TP1/Message Queue - Access | Y | |
SMTP server | Mail configuration | N |
JavaBeans resource | -- | N |
Other resources | Resource adapters conforming to the Connector 1.0 specifications or Connector 1.5 specifications | Y |