-
Bug
-
Resolution: Not a Bug
-
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.
- blocks
-
WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x
-
- Closed
-
- is cloned by
-
ENTMQBR-1614 [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
-
- Closed
-