[jboss-jira] [JBoss JIRA] (WFLY-10090) [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
Jeff Mesnil (JIRA)
issues at jboss.org
Fri Mar 30 09:44:01 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Mesnil updated WFLY-10090:
-------------------------------
Labels: activemq feature-branch-blocker (was: activemq)
> [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10090
> URL: https://issues.jboss.org/browse/WFLY-10090
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> Setting client globalThreadPoolSize for configuring max number of ActiveMQ-client-global-threads using system property or in connection factory which is looked up by standalone JMS client is ignored. There is alway 8 * number CPU cores.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list