Universal Connection Pool Not Handling Abandoned Connections Properly
Last updated on MARCH 08, 2017
Applies to:Universal Connection Pool - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When using UCP version 220.127.116.11, 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms