This content has been marked as final. Show 3 replies
Try setting the 'remove infected' to false. Either some application needs it, or the pool is continually finding
connections failing the simple pre-reserve test, and having to replace them. This is costing you performance...
We had disabled 'Test Connections On Reserve'.
But the 'Test Frequency' is set to 120 secs and 'Seconds to Trust an Idle Pool Connection' is set to 10 secs.
I am trying to check if that is the cause.
Test Table SQL being used with 'Test Frequency' is - "SELECT 1 FROM DUAL"... so its not the SQL issue.
Those aren't going to cause the 'problem', unless the connections are bad. 'Remove Infected Connections Enabled'=false is an important thing to try. The log should have indications of why connections are being closed. It may be simply that your pool is configured to allow shrinking, so it builds up a big number of connections when needed, and at downtimes, it closes them.