[jbossts-issues] [JBoss JIRA] Work logged: (JBTM-203) Interrupt reaper thread

Andrew Dinn (JIRA) jira-events at lists.jboss.org
Wed Jul 11 06:03:31 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBTM-203?page=worklog#action_12368552 ]

Andrew Dinn logged work on JBTM-203:

            Time Spent: 1 week, 1 day
    Remaining Estimate: 0 minutes
            Time Spent: 1 week, 1 day

added ReaperWorkerThread class
split TransactionReaper::check operation between ReaperThread calls (check) and ReaperWorkerThread (calls do_cancellations) synchronized via ReaperElement
added unit test class ReaperTestCase2

> 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.4
>          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


More information about the jbossts-issues mailing list