[
https://jira.jboss.org/browse/ISPN-556?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani commented on ISPN-556:
------------------------------------
No this is for transactions over Hot Rod, since it will involve the client participating
in an XA transaction but the server side just acting as a recipient for such commands. If
the link between client and server is severed and the client never comes back online
again, you have a stale tx on the server which is *not* registered with any JTA server to
perform a cleanup or recovery. And hence our own thread to do this.
house keeping of stale prepared transactions
--------------------------------------------
Key: ISPN-556
URL:
https://jira.jboss.org/browse/ISPN-556
Project: Infinispan
Issue Type: Feature Request
Components: Transactions
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.1.0.BETA1, 5.1.0.Final
We will need a background cleanup thread to clean up stale prepares and ongoing txs that
have exceeded a timeout (in cases where there is no backend TM and hence no recovery)
- Timeout could be set by user (cfg)
- Or by TM (XAResource.setTimeout())
Should also be able to release locks in this case
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira