I explored a little bit about it and found that in v5.6 this change was done.. https://issues.apache.org/jira/browse/AMQ-3667
Again coming back to the issue, I am now using pooled connection factory for my broker and seeing that this task thread is continuously getting created and destroyed. For example this is one of the thread name in my production environment: *ActiveMQ BrokerService[mqbrokerdev] Task-50456* thread names. Please note that at a time there are around 15-20 threads only but still why old threads are destroyed and new one's are getting created if ActiveMQ uses thread pool. Ideally It should keep one thread after it's job is done and assign the same thread for the next task. ?? Thanks, Anuj -- View this message in context: http://activemq.2283324.n4.nabble.com/What-is-the-effect-of-dedicatedTaskRunner-Attribute-tp2363191p4677924.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
