Universal Connection Pool Not Handling Abandoned Connections Properly
(Doc ID 1543165.1)
Last updated on MARCH 08, 2017
Universal Connection Pool - Version 220.127.116.11.0 and later Information in this document applies to any platform.
When using UCP version 18.104.22.168, calls to setAbandonedConnectionTimeout appear not to be getting honored. Attempts by the original requestor to use the same connection object (that should be reclaimed by the connection pool) are, erroneously, successful, indicating the connection object is still being used by that requestor. This can have ramifications if that same connection ends up getting used by another requestor.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!