]
Tomaz Cerar commented on WFLY-3663:
-----------------------------------
On releated topic, you should stop refering to executor in threads subsystem but rather
embed executor configuration from threads subsystem in ispn / jgrups subsystems.
WildFly should manage JGroups and Infinispan thread pools by default
--------------------------------------------------------------------
Key: WFLY-3663
URL:
https://issues.jboss.org/browse/WFLY-3663
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 8.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 9.0.0.Beta1
In our default configuration, both JGroups and Infinispan manage their own thread pools.
Unfortunately, both projects do not handle thread pool lifecycle so well. Both projects
use ExecutorService.shutdownNow() to end their thread pool lifecycles. This means that a
channel or cache can stop, but still leave active threads running (albeit interrupted).
We should have services that manage the lifecycle of our thread pools which ensure that
all threads have terminated during Service.stop().
This causes occasional OOMs in the Windows CI testsuite runs, due to too many threads
lying around.