Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 29.0.0.Alpha1, 29.0.0.Beta1, 29.0.0.Final
Affects Version/s: 28.0.0.Final
Component/s: Clustering
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly/pull/16861
[QE] How to address?:
---
[QE] Why QE missed?:
---

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.

causes

JBEAP-24271 Clustering: FATAL exception in heavyread scenario

Closed

JBEAP-24730 Clustering: FATAL error "thread pool is full" in ejb+servlet scenario

Closed

Assignee:: Paul Ferraro

Reporter:: Paul Ferraro

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2023/05/19 7:28 PM

Updated:: 2023/07/31 7:31 PM

Resolved:: 2023/05/23 10:48 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates