On 07/24/2013 12:43 PM, nnr_2k wrote:
Hi,
Could you please tell me is there a way to control the number of threads
spawned by activemq?
Basically, we are using IOtransport Configuration. By going through the
pstack, we have many threads for the process. Like:
IOtransport::run(),
TimerImpl::run(),
DedicatedTaskRunner::run(),
CompositeTaskRunner::run() .. etc
As per my understanding, IOtransport threads are used to marshall and
unmarshall the messages.
Do we really need a TimerImpl thread? is there anyway to stop these theads?
Thanks,
Narayana Reddy
--
View this message in context:
http://activemq.2283324.n4.nabble.com/controling-CompositeTaskRunner-and-DedicatedTaskRunner-threads-tp4669685.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
You can use NIO transport on the broker side to cut down on the number
of threads created on the broker side.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
