[infinispan-issues] [JBoss JIRA] Commented: (ISPN-272) Implement XA recovery in TransactionXaAdapter
[
https://issues.jboss.org/browse/ISPN-272?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-272:
------------------------------------
Also, Infinispan not responding to recover() properly can cause other resources in a
distributed transaction to fail or behave incorrectly. See this mail list thread for
details.
http://lists.jboss.org/pipermail/infinispan-dev/2010-December/007026.html
Look at (1) outlined in the email above.
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