[Bug 56310] PooledConnection and XAConnection not handled correctly

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=56310

Filip Hanik <fh...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Filip Hanik <fh...@apache.org> ---
(In reply to Jonathan Pierce from comment #0)
> For example, getPooledConnection().getConnection().close() should return the
> connection to the pool, not close the physical connection.

http://docs.oracle.com/javase/7/docs/api/javax/sql/ConnectionPoolDataSource.html#getPooledConnection()

-> Attempts to establish a physical database connection that can be used as a
pooled connection.


http://docs.oracle.com/javase/7/docs/api/javax/sql/PooledConnection.html#getConnection()

-> Creates and returns a Connection object that is a handle for the physical
connection that this PooledConnection object represents. 


Jonathan, thank you for your report. Overall, I do believe that the fix is that 
org.apache.tomcat.jdbc.pool.DataSource should NOT implement the
javax.sql.ConnectionPoolDataSource interface.

The ConnectionPoolDataSource/PooledConnection interface are to be used by pool,
instead of being provided by pool.

"An application programmer does not use the PooledConnection interface
directly; rather, it is used by a middle tier infrastructure that manages the
pooling of connections."

I'd like to learn more about your use case, and why it is using that interface
at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org