Hello, When you disable dedicatedTaskRunner the broker uses an internal thread pool just as you mentioned already. A thread from the pool will only be used when there is activity on the connection and will be returned to the pool when the connection is idle. So it will not use one thread per connection (only one thread per active connection) and generally the thread count should get reduced.
Hope this helps, Torsten Mielke tmielke.blogspot.com On 17 Jan 2014, at 09:48 am, khandelwalanuj <khandelwal.anu...@gmail.com> wrote: > Hi, > > Reference: > If we disable "dedicatedTaskRunner", we can use ActiveMQ internal thread > pool to control message dispatching. Using a thread pool can restrict the > number of threads required by ActiveMQ and hence reduce memory usage. > > Question: I disable "dedicatedTaskRunner", Will there not be one thread per > connection ? Which threads will be reduced. > > > Thanks, > Anuj >
