Read Timeout Error When Testing the Autonomous Database Connection
When testing the database connection, the Oracle Cloud Console can return a Read Timeout error after 90 seconds with the following exception:
Unable to test the connection Oracle_DB_Connection
("detail":**,"status":"HTTP 500 Internal Server Error",
"title":"io.micronaut.http.client.exceptions.ReadTimeoutException: Read
Timeout","type":"https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1")Verify that the database has not reached the maximum number of sessions.
When testing the connection, a new database session must be created. If the database has already reached its session limit, it cannot allocate a new session for the connection test. In this case, the database receives the request, but must wait for an existing session to be released before it can process it.
Oracle Integration waits up to 90 seconds for the connection test to complete; if the database does not process the request within this time, the operation times out.
The number of available sessions are tied to the base ECPU or OCPU count (75 SESSIONS per ECPU or 300 SESSIONS per OCPU).
See Service Concurrency.
Sessions: The number of sessions in the database.SessionUtilization: The maximum session utilization expressed as a percentage, aggregated across all consumer groups.
See Available Metrics: oci_autonomous_database.
To resolve the issue in the database, ensure that you have enough OCPUs or ECPUs allocated to the database instance.