Skip to main content

Source code revision

svn

summary: When max-connection-usage is enabled on a connection pool in a multi-threading scenario, there are possible chances of connection leaks. Modifying the way max connection usage operation is performed to fix this issue. Only when the resource's usage count is greater than the max connection usage count when max connection usage is set to a positive non-zero value, the resource handle will be removed from the pool. Fix for issue 17973.
revision: 51962
author: sm157516
date: 2012-01-09 10:08:09 UTC (5 years)
message: When max-connection-usage is enabled on a connection pool in a multi-threading scenario, there are possible chances of connection leaks. Modifying the way max connection usage operation is performed to fix this issue. Only when the resource's usage count is greater than the max connection usage count when max connection usage is set to a positive non-zero value, the resource handle will be removed from the pool. Fix for issue 17973.

Tests Run : Test case attached by user, JDBC devtests, QL
Change Path Actions
M branches/3.1.2/connectors/connectors-runtime/src/main/java/com/sun/enterprise/resource/pool/AssocWithThreadResourcePool.java
M branches/3.1.2/connectors/connectors-runtime/src/main/java/com/sun/enterprise/resource/pool/ConnectionPool.java
M branches/3.1.2/connectors/connectors-runtime/src/main/resources/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties
 
 
Close
loading
Please Confirm
Close