default thread pool in TaskRunnerFactory is initialized with a corePoolSize=0, i.e. no idle thread should be kept after keepAliveTime (works as coded)
I do not see a reason why you would want idle threads to be kept for a longer period, especially if there are several TaskRunnerFactory instances in use - this would simply leave idle threads in memory the idleTimeout (keepAliveTime, default 30) can be increased using a system property org.apache.activemq.thread.TaskRunnerFactory.keepAliveTime so that less thread recreation is needed depending on broker activity -- View this message in context: http://activemq.2283324.n4.nabble.com/What-is-the-effect-of-dedicatedTaskRunner-Attribute-tp2363191p4677933.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
