[
https://issues.jboss.org/browse/WFLY-11765?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-11765:
-----------------------------------------
The threads subsystem still exists and is shipped in WildFly. It's just not part of
our standard config. And it's definitely deprecated.
This doesn't make the basic point of this JIRA invalid -- we've got config
elements that relate to stuff whose use we discourage (and don't test) and don't
have alternatives.
Using the threads subsystem may work though if that's something you need working.
Documentation for configuration of thread pools out of date
-----------------------------------------------------------
Key: WFLY-11765
URL:
https://issues.jboss.org/browse/WFLY-11765
Project: WildFly
Issue Type: Bug
Reporter: James Guthrie
Assignee: Brian Stansberry
Priority: Major
The documentation in various subsystems (ejb, jca, batch-jberet) mention being able to
configure a thread-factory as part of a thread-pool configuration [1],[2],[3]. In the
schemas for the various components there is a reference to threads from the deprecated and
removed threads subsystem. It appears as though it is no longer possible to configure a
thread-factory at all in wildfly, and it is definitely not possible to provide a reference
to a component of the threads subsystem.
[1]:
https://wildscribe.github.io/WildFly/15.0/subsystem/batch-jberet/thread-p...
[2]:
https://wildscribe.github.io/WildFly/15.0/subsystem/jca/workmanager/defau...
[3]:
https://wildscribe.github.io/WildFly/15.0/subsystem/ejb3/thread-pool/inde...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)