You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Joachim Glink (JIRA)" <ji...@apache.org> on 2018/01/09 09:40:00 UTC

[jira] [Created] (AMQ-6883) Configuration issue if service wrapper is used

Joachim Glink created AMQ-6883:
----------------------------------

             Summary: Configuration issue if service wrapper is used
                 Key: AMQ-6883
                 URL: https://issues.apache.org/jira/browse/AMQ-6883
             Project: ActiveMQ
          Issue Type: Bug
            Reporter: Joachim Glink
            Priority: Minor


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
(v6.4.14#64029)