Hello.

The documentation
(http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html)
states that the DedicatedTaskRunner is disabled by default from 5.6 onwards.
This is true if the ActiveMQ is started directly, e.g. with "activemq.bat
start".

But if the ActiveMQ is started as a windows service from the wrapper.exe the
DedicatedTaskRunner is still activated because the wrapper.conf has
following entry:
wrapper.java.additional.8=-Dorg.apache.activemq.UseDedicatedTaskRunner=true

Question: is there a reason why the DedicatedTaskRunner is configured
differently for a standard AMQ start vs. service?
If so, can someone please explain it to me.

If the DedicatedTaskRunner should also be disabled for the service wrapper
than the default configuration should be changed accordingly.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Reply via email to