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

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554451#comment-13554451 ] 

Jeff Mesnil commented on WFLY-10090:
------------------------------------

[~clebertsuconic] do you tests in artemis that check how the thread pools grow?

>From the integration point of view, we passed the correct settings to Artemis.

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