Hello
We have a 20.3 ORDS installation with a default setting for the 'jdbc.InactivityTimeout' parameter for all pools . This default value is 1800 seconds. It appears that this setting is not working correctly based on the sessions shown in the v$session view in the underlying database. Shown below are the connections and the time in seconds since they were last active (last_call_et) .
APEX_REST_PUBLIC_USER 29
APEX_REST_PUBLIC_USER 29
APEX_REST_PUBLIC_USER 29
APEX_REST_PUBLIC_USER 196
APEX_REST_PUBLIC_USER 463
APEX_REST_PUBLIC_USER 2401
APEX_REST_PUBLIC_USER 3990
APEX_REST_PUBLIC_USER 3990
APEX_REST_PUBLIC_USER 3990
Also, from the JVM monitoring tool we see the following for the apex_rt pool
totalConnectionsCount=10
remainingPoolCapacityCount=0
borrowedConnectionsCount=0
At times we end up having to restart ORDS because we encounter this error
ORDS was unable to make a connection to the database. This can occur if the database is unavailable, the maximum number of sessions has been reached or the pool is not correctly configured. The connection pool named: |apex|rt| had the following error(s): Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Universal Connection Pool is about to shutdown: low chance to get a connection
Any idea what may be happening here ? Is ORDS leaking connections ?
Thanks !
Varad