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