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

[Justin Bertram (JIRA)]

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

Justin Bertram commented on WFWIP-20:
-------------------------------------

Despite the fact that the test passes with on Wildfly master, I still think there's a problem with the test.  If {{testConnectionFactoryPools}} is executed last or not executed at all the other tests pass.

> [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
> ------------------------------------------------------------------------------------------------
>
>                 Key: WFWIP-20
>                 URL: https://issues.jboss.org/browse/WFWIP-20
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Artemis
>            Reporter: Miroslav Novak
>            Assignee: Martyn Taylor
>            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)