Bug 1275362 - [SET] (6.4.z) Change default thread pool rejection policy to "abort"
[SET] (6.4.z) Change default thread pool rejection policy to "abort"
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Romain Pelisse
Jitka Kozana
Depends On:
Blocks: 1235746
  Show dependency treegraph
Reported: 2015-10-26 12:22 EDT by Romain Pelisse
Modified: 2016-02-08 09:35 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-08 09:01:55 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker JGRP-1965 Major Resolved Change default thread pool rejection policy to "abort" 2017-01-17 06:52 EST

  None (edit)
Description Romain Pelisse 2015-10-26 12:22:58 EDT
Description of problem:

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 has already been fixed upstream and documented in JGRP-1965(https://issues.jboss.org/browse/JGRP-1965). Discussing it with Paul Ferraro, we thought it would be quite relevant to backport in EAP 6.

Version-Release number of selected component (if applicable):


Note You need to log in before you can comment on or make changes to this bug.