-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b167
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8179803 | 10 | Lance Andersen | P4 | Resolved | Fixed | b07 |
Minor clarification of the PooledConnection javadoc for clarity when shared connections are used in a Java EE environment via the Connector API
Change:
If the connection pool manager wraps or provides a proxy to the logical handle returned from a call to PoolConnection.getConnection, the pool manager must do one of the following when the application calls Connection.close:
to:
If the connection pool manager wraps or provides a proxy to the logical handle returned from a call to PoolConnection.getConnection, the pool manager must do one of the following when the connection pool manager closes or returns the PooledConnection to the pool in response to the application calling Connection.close:
Change:
If the connection pool manager wraps or provides a proxy to the logical handle returned from a call to PoolConnection.getConnection, the pool manager must do one of the following when the application calls Connection.close:
to:
If the connection pool manager wraps or provides a proxy to the logical handle returned from a call to PoolConnection.getConnection, the pool manager must do one of the following when the connection pool manager closes or returns the PooledConnection to the pool in response to the application calling Connection.close:
- backported by
-
JDK-8179803 Minor update to the PooledConnection javadoc
-
- Resolved
-