XA END / un-enlist for database connection call...| JBoss.org Content Archive (Read Only)

This project is read only now. Read more.

1 2 Previous Next 17 Replies Latest reply on Sep 3, 2014 10:24 AM by smarlow Go to original post

15. Re: XA END / un-enlist for database connection called to early

jesper.pedersen Sep 2, 2014 10:50 AM (in response to aliebscher)

Transaction.delistResource(XAResource, flag) occurs in a beforeCompletion() implementation -- enlistResource and delistResource are required to be called as a pair. The IronJacamar system property disables the delistResource() call, and hence violates the specification.

See up-thread reply on how to integrate the change.

Frank, you need to investigate why that happens - could be a bug in the XAResource implementation of either of the components.
Actions
16. Re: XA END / un-enlist for database connection called to early

smarlow Sep 2, 2014 1:52 PM (in response to aliebscher)

Andreas Liebscher wrote:

Any idea when there will be a released fix available?

In what WF release version?

We need to get further in our discussion about how to ensure that the Ironjacamar Synchronization.beforeCompletion is run after other interposed Synchronization call backs.
Actions
17. Re: XA END / un-enlist for database connection called to early

smarlow Sep 3, 2014 10:24 AM (in response to smarlow)

I reopened WFLY-3619, as that best describes the current blocker.
Actions

1 2 Previous Next