[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-1074) TransactionXaAdapter.commit with onePhase=true doesn't rollback when tx is marked rollbackOnly

[Manik Surtani (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani resolved ISPN-1074.
---------------------------------

    Fix Version/s: 4.2.2.BETA1
       Resolution: Done


> TransactionXaAdapter.commit with onePhase=true doesn't rollback when tx is marked rollbackOnly
> ----------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1074
>                 URL: https://issues.jboss.org/browse/ISPN-1074
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Transactions
>    Affects Versions: 4.2.0.Final
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>            Priority: Critical
>              Labels: 1PC, JTA
>             Fix For: 4.2.2.BETA1, 4.2.2.FINAL, 5.0.0.CR2, 5.0.0.FINAL
>
>
> Scenario: use eager locking with lockSingleNode=true. Start a transaction and kill a node where a lock is acquired. Then commit the transaction using JBossTM. As there's only one transaction enlisted, JBossTM optimizes the 2PC and only invokes TransactionXAAdaptr.commit with onePhase flag set to true. Right now this call results in an exception that leaves the cluster with locks being acquired. Instead of this, infinispan should rollback the transaction and throw an exception(XA_HEURRB?) that would be propagated to the user as well.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira