[jbossts-issues] [JBoss JIRA] (JBTM-1485) Change reaper to dump the resources that are stuck and stacks of stuck threads

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Mon Sep 23 03:21:03 EDT 2013

    [ https://issues.jboss.org/browse/JBTM-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806330#comment-12806330 ] 

Tom Jenkinson commented on JBTM-1485:

No, it just logs the stack trace of the reaper element when it detects that the reaperelement is stuck. It helps clarify for the user that the reaper element is stuck in a drivers code.

The change is here: https://source.jboss.org/browse/Narayana/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/TransactionReaper.java?r2=741403a577ddb1867b0c473bd52087c935a95616&r1=bc9a3668c4ed6e8c52f6b2c3d4596e115c12ccf8
> Change reaper to dump the resources that are stuck and stacks of stuck threads
> ------------------------------------------------------------------------------
>                 Key: JBTM-1485
>                 URL: https://issues.jboss.org/browse/JBTM-1485
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Core
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>            Priority: Minor
>             Fix For: 5.0.0.M5
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> Dump the wedged reaperelements stack if it is still in state cancel

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list