Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 30.0.0.Beta1, 30.0.0.Final
Affects Version/s: 29.0.1.Final
Component/s: None
Labels:
None

Steps to Reproduce:
- Start Wildfly / JBoss EAP server,
- run :reload operation repeatedly,
- check in a profiler tool that multiple ThreadGroups with identical names are being created.
Git Pull Request:
https://github.com/wildfly/wildfly/pull/17194, https://github.com/wildfly/wildfly/pull/17193, https://github.com/wildfly/wildfly/pull/17243
[QE] How to address?:
---
[QE] Why QE missed?:
---

There is a fresh set of thread groups being created on each server reload, with identical names as groups that already exist from before, e.g. "LocalScheduler", "SchedulerTopologyChangeListener", "default-threads", "Weld ThreadGroup" and others.

Can these groups be kept in static fields so that the same instances can be reused?

is cloned by

JBEAP-25718 (7.4.z) Avoid creating duplicate thread groups on server reload

Verified

JBEAP-25717 (8.0.z) Avoid creating duplicate thread groups on server reload

Closed

relates to

WFCORE-6505 Avoid creating duplicate thread groups on server reload

Resolved

JBEAP-25818 (8.0.z) WFCORE-6505 Avoid creating duplicate thread groups on server reload

Closed

Assignee:: Tomas Hofman

Reporter:: Tomas Hofman

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2023/09/18 9:44 AM

Updated:: 2023/12/10 2:52 AM

Resolved:: 2023/09/20 10:34 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates