[infinispan-issues] [JBoss JIRA] Updated: (ISPN-272) Implement XA recovery in TransactionXaAdapter

[Manik Surtani (JIRA)]

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

Manik Surtani updated ISPN-272:
-------------------------------

    Summary: Implement XA recovery in TransactionXaAdapter  (was: recover from transaction failures)


Some more comments.

Currently, TransactionXaAdapter.recover() is a no-op.  It should:

1) Stop the cache (prevent any more txs from starting)
2) Roll back existing txs
3) Release any locks
4) Wipe in-memory state
5) Restart the node so it re-joins the cluster and gets a fresh copy of state



> Implement XA recovery in TransactionXaAdapter
> ---------------------------------------------
>
>                 Key: ISPN-272
>                 URL: https://issues.jboss.org/browse/ISPN-272
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Transactions
>    Affects Versions: 4.0.0.Final
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 5.0.0.BETA1, 5.0.0.Final
>
>
> We currently don't support any sort of recovery from transaction failures.
> E.g.
> tm.start();
> database.delete(account);
> ispnCache.put(account);
> tm.commit():
> At tm commit:
> -prepare is successful on both enlisted resources.
> - database.commit - fails
> What shall we do with the locks/state from ispnCache.
> Possible solutions:
>  - configure to automatically commit/rollback after a timeout
>  - keep locks on resources and allow manual intervention through JMX
>  - others?

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