[jboss-jira] [JBoss JIRA] (WFLY-10090) [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored

[Miroslav Novak (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Novak moved JBEAP-14473 to WFLY-10090:
-----------------------------------------------

           Project: WildFly  (was: JBoss Enterprise Application Platform)
               Key: WFLY-10090  (was: JBEAP-14473)
          Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
       Component/s: JMS
                        (was: JMS)
    Target Release:   (was: 7.backlog.GA)


> [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
>
> 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)