[JBoss-dev] JBoss 3.2 problem with trackConnectionByTx and jdbc xa datasources

[Igor Fedorenko]

Hi,

There is a problem with trackConnectionByTx in the current CVS version
of JBoss 3.2 which occurs when two beans access the same datasource
from the same transaction. I am not 100% sure about original implementation intends and would like to give others an opportunity to complain before I check in updated trackConnectionByTx logic.
Consider the following example

- BeanA allocates a connection and gets an instance conn1
- BeanA calls BeanB
- BeanB allocates a connection and gets the same instance conn1
- BeanB closes the connection and returns
- BeanA tries to use the connection and gets SQLException("Logical
handle is closed").

Updated trackConnectionByTx logic will return the
same connection only if the connection has not been allocated yet
(condition
"BaseConnectionManager2.ConnectionListener.isManagedConnectionFree()");
otherwise allocate and return new connection.

Any objections?

--
Igor Fedorenko
Think smart. Think automated. Think Dynamics.
www.thinkdynamics.com




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development