]
Martin Simka moved JBEAP-4611 to WFCORE-1559:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1559 (was: JBEAP-4611)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: Server)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 2.1.0.Final
(was: 7.0.0.GA)
"default" as default name for long-running-threads and
short-running-threads leads to thread groups with the same name default-threads
---------------------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-1559
URL:
https://issues.jboss.org/browse/WFCORE-1559
Project: WildFly Core
Issue Type: Enhancement
Components: Server
Affects Versions: 2.1.0.Final
Reporter: Martin Simka
Assignee: Jason Greene
Priority: Minor
/subsystem=jca/workmanager=default/short-running-threads=default
/subsystem=jca/workmanager=default/long-running-threads=default
Thread group with name {{default-threads}} is created for both of these addresses.
It's because thread group name is created from last element of resource's address
+ string {{-threads}}.
[
ThreadPoolManagementUtils.java#L166|https://github.com/wildfly/wildfly-co...]
{code:java}
params.name = pathAddress.getLastElement().getValue();
{code}
[
ThreadFactoryResolver.java#L149|https://github.com/wildfly/wildfly-core/b...]
{code:java}
protected String getThreadGroupName(String threadPoolName) {
return threadPoolName + "-threads";
}
{code}
Thread groups for different resources shouldn't have the same name. Also such a
general name {{default-threads}} could be confusing when debugging.