[
http://jira.jboss.com/jira/browse/JBTM-203?page=all ]
Jonathan Halliday closed JBTM-203.
----------------------------------
Fix Version/s: 4.3.0.BETA2
(was: 4.4)
Resolution: Done
Interrupt reaper thread
-----------------------
Key: JBTM-203
URL:
http://jira.jboss.com/jira/browse/JBTM-203
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.2
Reporter: Mark Little
Assigned To: Andrew Dinn
Fix For: 4.3.0.BETA2
Time Spent: 1 week, 1 day
Remaining Estimate: 0 minutes
It is possible for the reaper thread to become blocked when telling a transaction to
rollback. We should have another thread that interrupts the reaper thread if it has been
blocked for more than a configurable amount of time on the same transaction. In this case,
the reaper could either put the transaction back on the list and try again later, or just
mark it as rollback_only. My preference would actually be to have a separate list of
blocked transactions that are marked as rollback_only and have the reaper try to roll them
back again later.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira