[jboss-jira] [JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads

[Radim Vansa (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radim Vansa updated JGRP-1574:
------------------------------

    Description: 
Sometimes I find out my OOB threadpool size (which defaults to 200) in our tests too low, causing deadlock (this seems to be the case with the 64 node cluster - we've run out of OOB threads because all of them were stuck).
New rejection policy could usually silently discard the message, but in case that the thread pool does not finish anything (getCompletedTaskCount stays constant) for a period, it would throw a special exception denoting that there's possibly a deadlock (and that raising OOB threadpool could help).

    
> ThreadPool rejection policy detecting stuck threads
> ---------------------------------------------------
>
>                 Key: JGRP-1574
>                 URL: https://issues.jboss.org/browse/JGRP-1574
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Radim Vansa
>            Assignee: Radim Vansa
>            Priority: Minor
>
> Sometimes I find out my OOB threadpool size (which defaults to 200) in our tests too low, causing deadlock (this seems to be the case with the 64 node cluster - we've run out of OOB threads because all of them were stuck).
> New rejection policy could usually silently discard the message, but in case that the thread pool does not finish anything (getCompletedTaskCount stays constant) for a period, it would throw a special exception denoting that there's possibly a deadlock (and that raising OOB threadpool could help).

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