https://issues.apache.org/bugzilla/show_bug.cgi?id=56310
Bug ID: 56310
Summary: PooledConnection and XAConnection not handled
correctly
Product: Tomcat Modules
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P2
Component: jdbc-pool
Assignee: dev@tomcat.apache.org
Reporter: jonathan.d.pie...@chase.com
Currently calls to getPooledConnection() and getXAConnection on the pooled
DataSource return the same handler as calls to getConnection().
This does not correctly implement these interfaces.
Per the documentation
(http://docs.oracle.com/javase/6/docs/api/javax/sql/PooledConnection.html):
"A PooledConnection object represents a physical connection to a data source"
and the documentation for the close method:
"Closes the physical connection that this PooledConnection object represents.
An application never calls this method directly; it is called by the connection
pool module, or manager."
The getPooledConnection() and getXAConnection() methods should return the
physical connection provided by the driver (if it implements the interface),
wrapped in a handler that will provide the pool handler when the
getConnection() method is called.
For example, getPooledConnection().getConnection().close() should return the
connection to the pool, not close the physical connection.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
