[jboss-jira] [JBoss JIRA] Updated: (JBAS-5079) Add a stuck thread feature to the application server that scans for stuck threads

Thu May 22 05:41:51 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBAS-5079?page=all ]

Dimitris Andreadis updated JBAS-5079:
-------------------------------------

    Component/s: Management services
                     (was: Other)

> Add a stuck thread feature to the application server that scans for stuck threads
> ---------------------------------------------------------------------------------
>
>                 Key: JBAS-5079
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5079
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Management services
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Jay Howell
>
> Many Other application servers have a stuck thread reaper that looks at threads and the times that they have been taking.  If they take too long they are either logged as a warning or they are killed.  This is a very dangerous safeguard, but it's a feature that does come in quite handy if a thread gets stuck on an object lock.  We've seen some of these in support especially around the Jbosscache when customers misconfigure JbossCache with ejb3/hibernate.  It also happens with customers do strange things with jms inside the app server. 
> The configuration might be something like.
> StuckThreadInterval - interval at which the scanner should scan for stuck threads.  Higher amounts will give more time before the event(log or inturrupt) is fired. -1 means it's disabled.
> StuckThreadNotification - class to be called if a thread gets stuck default would be org.jboss....StuckThreadLogger
> the default behavior should log the stuck thread.
> But we should also have another class that can be plugged in the StuckThreadNotification that inturrups the thread.  Maybe we can call it org.jboss.....StuckThreadInturrupter
> Log should always log it, but with a configuration change, it should be able to inturrupt it.
> We've had multiple requests for this feature.

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