Details
-
Bug
-
Resolution: Done
-
Blocker
-
28.0.0.Final
-
None
Description
JGroups 5.2 changed up its thread pool configuration logic within its transport protocols and overwrites the thread pool implementation provided via TP.setThreadPool(...)
This causes JGroups to run with a max-threads of 100, whereas our default is 200 threads, as well as ignoring our overridden rejection policy.
Attachments
Issue Links
- causes
-
JBEAP-24271 Clustering: FATAL exception in heavyread scenario
- Closed
-
JBEAP-24730 Clustering: FATAL error "thread pool is full" in ejb+servlet scenario
- Closed