1b5396c033
1. Changed public fields in ActiveMQClient to private and added getters. Exposing fields for thread pool sized allow to modify them in undesired ways. I made these fields private and added corresponding getter methods. In addition, I renamed the field 'globalThreadMaxPoolSize' to 'globalThreadPoolSize' to be more consistent with the 'globalScheduledThreadPoolSize' field name. I also adapted some tests to always call clearThreadPools after the thread pool size configuration has been changed. 2. Protect against injecting null as thread pools ActiveMQClient.injectPools allowed null as injected thread pools. The effect was that internal threads pools were created, but not shutdown correctly. |
||
---|---|---|
.. | ||
activemq5-unit-tests | ||
config | ||
extra-tests | ||
integration-tests | ||
jms-tests | ||
joram-tests | ||
performance-tests | ||
soak-tests | ||
stress-tests | ||
timing-tests | ||
unit-tests | ||
pom.xml |