[
https://issues.jboss.org/browse/WFLY-10090?page=com.atlassian.jira.plugin...
]
Jeff Mesnil commented on WFLY-10090:
------------------------------------
[~mnovak] I have debugged the code of the messaging-activemq subsystem that pass the 2
pool size to Artemis and I see that the call to
ActiveMQClient.setGlobalThreadPoolProperties uses the expected values at
https://github.com/jmesnil/wildfly/blob/WFLY-9407_upgrade_artemis_2.4.0_w...
I also noted that the testGlobalPoolsConfiguredBySystemProperty and
testGlobalPoolsConfiguredByAttributeInMessagingSubsystem tests passes when they are run
separately.
Could there be an issue with the way threads are measured (e.g. and accumulated across
tests)?
[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)