A bit more.
What is actually happening is because the tests required to matchManagedConnections to
fail, when the test originally runs, the pool is empty. A connection is successfully
created and enlisted/delisted in the tranasction and returned to the pool. The second
attempt to acquire the connection fails in the match and the connection is destroeyd.
Howerve,r JBossTS rightfully 'remembers' this guy and when JBossTS attempts to
finish the txn protocol the connection has already been destroyed. This is where the error
occurs. So, effectively the <track-connection-by-txn> really should be here and in
fact, I believe it's a bug that it's not.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006519#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...