Bugs item #731359, was opened at 2003-05-02 14:06 Message generated for change (Settings changed) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=731359&group_id=22866
Category: JBossMQ Group: v3.2 >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Mark Little (marklittle) Assigned to: Adrian Brock (ejort) Summary: Transaction termination and disassociation assumption Initial Comment: The TransactionManagerStrategy inner class of org.jboss.mq.pm.jdbc2.PersistenceManager uses a javax.transaction.Transaction instance to terminate the transaction. However, if a transaction is terminated in this way, it doesn't have to affect the thread-to- transaction association. So, if the terminating thread has this transaction as it's "current" transaction then it'll still be associated with it after commit/rollback returns, even though the transaction is now dead. This can then cause problems later on. The fact that the JBoss transaction implementation does to a thread-disassociation is not typical of other transaction implementations, so it would probably be better to call suspend after termination or use TransactionManager. Mark. ---------------------------------------------------------------------- Comment By: Adrian Brock (ejort) Date: 2003-05-31 01:10 Message: Logged In: YES user_id=9459 Fixed in 3.2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=731359&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
