Details
-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Undefined
Description
Note: this JIRA doesn't cover the scenario where recovery is enabled (XA transactions) since it has its own recovery operation compliant with JTA.
Note2: hot rod transaction is out of this scope.
Add a management interface (JMX, CLI & REST) to interact with GlobalTransaction ids, which are unique in the Infinispan instance. The following operation may be useful
- list: list all local GlobalTransaction and its transaction status
- get: receives a GlobalTransaction id and retrieves any information about it: Transaction's xid, Transaction's status, number of locked keys?, nodes involved?
- forceRollback: receives a GlobalTransaction's id and rollbacks the transaction. If the Transaction status is committed, it does nothing; otherwise, it sends the rollback. If a Transaction does not exist, just broadcast TxCompletionNotificationCommand to release any "leaked" resources.