[jboss-jira] [JBoss JIRA] (JGRP-1965) Change default thread pool rejection policy to "abort"

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JGRP-1965:
-----------------------------------------------

Romain Pelisse <rpelisse at redhat.com> changed the Status of [bug 1275362|https://bugzilla.redhat.com/show_bug.cgi?id=1275362] from POST to MODIFIED

> Change default thread pool rejection policy to "abort"
> ------------------------------------------------------
>
>                 Key: JGRP-1965
>                 URL: https://issues.jboss.org/browse/JGRP-1965
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.6.6
>            Reporter: Paul Ferraro
>            Assignee: Bela Ban
>             Fix For: 3.6.7
>
>
> Currently, JGroups transport thread pools use discard as a rejection policy.  Thus if there are no available threads, and the queue is full, the executor will silently drop the task.
> Abort will throw a RejectedExecutionException, in which case, which JGroups catches to populate the num_rejected_msgs statistic.  This is a better default, so that users can monitor this value to determine whether or not to modify their thread pool configuration.  Otherwise, num_rejected_msgs is 0, which might be a source of confusion.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)