Bugs item #585632, was opened at 2002-07-23 18:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=585632&group_id=22866
Category: JBossTX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Igor Fedorenko (igorfie) Assigned to: Nobody/Anonymous (nobody) Summary: Problem with XA and Oracle Initial Comment: org.jboss.tm.TxCapsule#enlistResource(XAResource) has an optimization that is not compatible with Oracle. The problem occurs only when more then one connections to same database server try to participate in same distributed transaction. Here what happens 1. First db connection joins transaction; TxCapsules sees new resource manager/transaction pair and calls XAResource#start(xid1, XAResource.TMNOFLAGS); everything works fine. 2. When second db connection tries to join the transaction TxCapsule sees same RM/transaction pair and tries to call XAResource#start(xid1, XAResource.TMJOIN) to attach second connection to the transaction. This is not supported by Oracle and the call fails with XA_RETRY error code. It should be possible to turn this optimization on/off on per RM basis. As a temporary workaround I would disable this optimization (unless some other RM does not work without it). I am running Branch_3_0 on Win2k, JDK 1.3.1_04, Oracle 8173. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=585632&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
