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.