[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka edited comment on JBTM-2124 at 12/6/17 1:38 AM: ---------------------------------------------------------------- Discussion at the https://developer.jboss.org/message/971613 gives more details about needs for this fix. My conversation with Jonathan during F2F gives me a bit more details about what his proposal meant {quote ... ensure the node name is getting into the Xid (it probably already is), ensure the existing name filter can read it (it probably can), add ownership filter(s) as necessary... {quote} What I was not sure what is the ownership filter - that's mean filter which defines if the transaction is not inflight one. The order of {{XAResourceOrphanFilter}} (orphan filters are lauched by XARecoveryModule) to veto rollback (in case) should be similar what JTA does in way (example from JTA): NodeNameXAResourceOrphanFilter (was transaction created by me?), JTATransactionLogXAResourceOrphanFilter (is not this transaction subordinate?), JTAActionStatusServiceXAResourceOrphanFilter (is not this transaction in-fligth?) The picture https://issues.jboss.org/secure/attachment/12428637/jonathan-picturing-tr... shows the test scenario which needs to be considered which is about writing parent and child to the same database. Both are of the same transaction but each of the Xid record belongs to different server. The Xid of {{#2}} has to be resolved by {{Child}}. If {{Parent}} tries to resolve it then it would vote to rollback as it does have no record in parent's log store (the record was created by child). was (Author: ochaloup): Discussion at the https://developer.jboss.org/message/971613 gives more details about needs for this fix. My conversation with Jonathan during F2F gives me a bit more details about what his proposal meant {quote ... ensure the node name is getting into the Xid (it probably already is), ensure the existing name filter can read it (it probably can), add ownership filter(s) as necessary... {quote} What I was not sure what is the ownership filter - that's mean filter which defines if the transaction is not inflight one. The order of {{XAResourceOrphanFilter}} to veto rollback (in case) should be similar what JTA does in way (example from JTA): NodeNameXAResourceOrphanFilter (was transaction created by me?), JTATransactionLogXAResourceOrphanFilter (is not this transaction subordinate?), JTAActionStatusServiceXAResourceOrphanFilter (is not this transaction in-fligth?) The picture https://issues.jboss.org/secure/attachment/12428637/jonathan-picturing-tr... shows the test scenario which needs to be considered which is about writing parent and child to the same database. Both are of the same transaction but each of the Xid record belongs to different server. The Xid of {{#2}} has to be resolved by {{Child}}. If {{Parent}} tries to resolve it then it would vote to rollback as it does have no record in parent's log store (the record was created by child). -- This message was sent by Atlassian JIRA (v7.5.0#75005)