activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From khandelwalanuj <khandelwal.anu...@gmail.com>
Subject Re: OptimizedDispatch and DedicatedTaskrunner
Date Tue, 11 Feb 2014 11:30:23 GMT
Hey,

So If I use optimize dispatch there will not be one thread per queue for
message dispatching; than how does the message dispatch processing will
happen. (I am using dedicated task runner which is by default )

AND

I am little bit confused here. I have my thread trace here which is pasted
below:

I have tested by disabling dedicated task runner in my setup but not found
any thread reduction. 
Can you tell me which threads are going to reduce in below thread trace if I
disable dedicatedTaskRunner ? 


    45  5           0           0           0           0 KahaDB Scheduler
    46  5          16          16          10          10 ActiveMQ Journal
Checkpoint Worker
    47 10           2           2           0           0 ActiveMQ Data File
Writer
    48  5           1           1           0           0 KahaDB Scheduler
    49  5          21          21          10          10 ActiveMQ Journal
Checkpoint Worker
    50 10           2           2           0           0 ActiveMQ Data File
Writer
    51  5           0           0           0           0 ActiveMQ Durable
Subscriber Cleanup Timer
    53  5          19          19          10          10 StatsCollector-1
    54  5           1           1           0           0 KahaDB Scheduler
    55 10           4           4           0           0 ActiveMQ Data File
Writer
    69  8          56          56          50          50 ActiveMQ Transport
Server Thread Handler:
tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000
    70  9           6           6           0           0 ActiveMQ Transport
Server: tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000
    71  8           6           6           0           0 ActiveMQ Transport
Server Thread Handler:
nio://0.0.0.0:61615?wireFormat.maxInactivityDuration=30000
    72  9          11          11           0           0 ActiveMQ Transport
Server: nio://0.0.0.0:61615?wireFormat.maxInactivityDuration=30000
    73  8           5           5           0           0 ActiveMQ Transport
Server Thread Handler:
stomp://0.0.0.0:61613?transport.defaultHeartBeat=5000,0
    74  9           5           5           0           0 ActiveMQ Transport
Server: stomp://0.0.0.0:61613?transport.defaultHeartBeat=5000,0
    75  8           5           5           0           0 ActiveMQ Transport
Server Thread Handler:
stomp+nio://0.0.0.0:61614?wireFormat.maxInactivityDuration=30000
    76  9           8           8           0           0 ActiveMQ Transport
Server: stomp+nio://0.0.0.0:61614?wireFormat.maxInactivityDuration=30000
    78  5          23          23          20          20 ActiveMQ
BrokerService[hydmqbrokerdev] Task-1
    79  5          86          86          80          80 ActiveMQ
Transport: tcp:///149.77.164.100:57252@61616
    80  5          28          28          20          20 ActiveMQ
BrokerService[hydmqbrokerdev] Task-2
    81  5           2           2           0           0 ActiveMQ
InactivityMonitor ReadCheckTimer
    82  5           6           6           0           0 ActiveMQ
InactivityMonitor WriteCheckTimer
    83  5          10          10           0           0 ActiveMQ
Transport: tcp:///149.77.164.100:57261@61616
    84  5          17          17          10          10 ActiveMQ
Transport: tcp:///149.77.164.100:57301@61616
    85  5          20          20          10          10 ActiveMQ
Transport: tcp:///149.77.164.100:57306@61616
    89  5           1           1           0           0 ActiveMQ
InactivityMonitor Worker


Thanks,
Anuj



--
View this message in context: http://activemq.2283324.n4.nabble.com/OptimizedDispatch-and-DedicatedTaskrunner-tp4676820p4677774.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message