[ https://issues.apache.org/jira/browse/AMQ-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Pavlovich updated AMQ-6883: -------------------------------- Affects Version/s: 5.15.14 > Configuration issue if service wrapper is used > ---------------------------------------------- > > Key: AMQ-6883 > URL: https://issues.apache.org/jira/browse/AMQ-6883 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.15.14 > Reporter: Joachim Glink > Assignee: Matt Pavlovich > Priority: Minor > Fix For: 5.17.0 > > Attachments: JIRA_AMQ_6883.patch > > > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)