I want to understand why you are getting the problem in
the first place.
The code change simply sidesteps the issue. It matches
the logic in JCA with the check done in JTA.
If JTA does not allow it, there is no point JCA trying it.
But why do you still have a currentTx when you try to close the
connection? What is the relative ordering of the afterCompletions
and what is the value of {is/was}trackByTx?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853539#3853539
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853539
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
