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

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

    [ https://issues.apache.org/jira/browse/AMQ-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341282#comment-16341282 ] 

Surya Prakash Raja commented on AMQ-6883:
-----------------------------------------

Hello,

I have created a patch for modifying the wrapper configurations for all operating systems to be consistent with the JIRA(https://issues.apache.org/jira/browse/AMQ-3667).

Surya

> 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
(v7.6.3#76005)