[
https://issues.jboss.org/browse/WFWIP-20?page=com.atlassian.jira.plugin.s...
]
Justin Bertram commented on WFWIP-20:
-------------------------------------
I was able to reproduce the failure using the steps provided. However, I wanted to focus
on the system property test so I ran that one by itself:
{noformat}
mvn clean test -Dtest=ClientThreadPoolTestCase#testGlobalPoolsConfiguredBySystemProperty
-Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT
-DfailIfNoTests=true | tee log
{noformat}
As Jeff noted, the test runs, but it doesn't fail. I ran it several times and it
always passed. I suspect there may be an issue with the test itself.
[~jmesnil], I also looked into
{{org.apache.activemq.artemis.ClientThreadPoolsTest#testSystemPropertyThreadPoolSettings}}
in the Artemis code-base and it passes as expected.
[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)