[AMQ-6883] Configuration issue if service wrapper is used

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.15.14
• Fix Version/s: 5.17.0, 5.16.5
• Assignee: Matt Pavlovich
• Reporter: Joachim Glink
• Created: 09/Jan/18 09:39
• Updated: 23/Feb/22 17:33
• Resolved: 23/Feb/22 17:33

Description

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

Please make the default configuration of AMQ similar across all start-ups.

see mailing list entry: http://activemq.2283324.n4.nabble.com/UseDedicatedTaskRunner-configuration-td4734704.html