[
https://issues.jboss.org/browse/WFLY-6590?page=com.atlassian.jira.plugin....
]
Miroslav Novak moved JBEAP-4539 to WFLY-6590:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6590 (was: JBEAP-4539)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: JMS)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 10.0.0.Final
(was: 7.0.0.ER6)
Client thread pool max size parameter should be possible to
parametrize in CLI
------------------------------------------------------------------------------
Key: WFLY-6590
URL:
https://issues.jboss.org/browse/WFLY-6590
Project: WildFly
Issue Type: Feature Request
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
Based on discussion in JBEAP-2947, we should provide CLI parameter to set maximum size of
client thread pool.
Currently {{-Dactivemq.artemis.client.global.thread.pool.max.size=<value>}} must be
provided as system property during start of EAP 7 server.
This thread pool can be injected by Wildfly. This could be the way to limit make its size
configurable by Wildfly
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)