According the following documentation, sessions should remain active indefinitely (maxIdleTime = 0 and maxConnectionAge = 0) and they should test connectivity every 10 minutes with the following request "select 1 from dual" (preferredTestQuery) to check if database is alive.
Currently, we see that all the sessions are reconnected in 10 minutes (600 seconds).
We also checked the link : https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/congw-10-0/reference/troubleshoot-the-gateway/troubleshoot-problems-and-solutions.html#concept.dita_7109cd1681768c1f105f6181bb22ebf66186963b_ProblemJDBCconnectionfailures
And this link : https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/congw-10-0/security-configuration-in-policy-manager/tasks-menu-security-options/manage-jdbc-connections/set-jdbc-connection-properties.html
Release: API Gateway 10.x
We normally recommend that our customers set their JDBC connection configurations to look like the following:
NOTE: For each thread in the pool size, the Gateway will use 8MB of RAM to hold this connection - so for the example 8X15=120MB