[
https://issues.redhat.com/browse/ISPN-12735?page=com.atlassian.jira.plugi...
]
Dan Berindei edited comment on ISPN-12735 at 2/16/21 7:13 AM:
--------------------------------------------------------------
It would be great if the transaction table also kept track of when a particular
transaction was started. That way the *list* operation could have an optional duration
parameter, only listing transactions older than duration seconds.
was (Author: dan.berindei):
It would be great if the transaction table also kept track of when a particular
transaction was started. That way the **list** operation could have an optional duration
parameter, only listing transactions older than duration seconds.
Simple transaction recovery operation
-------------------------------------
Key: ISPN-12735
URL:
https://issues.redhat.com/browse/ISPN-12735
Project: Infinispan
Issue Type: Enhancement
Components: Transactions
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
Priority: Major
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.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)