You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2009/08/29 07:53:15 UTC

[jira] Assigned: (AMQ-2368) it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf

     [ https://issues.apache.org/activemq/browse/AMQ-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-2368:
-------------------------------

    Assignee: Rob Davies

> it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf
> -----------------------------------------------------------------------------------
>
>                 Key: AMQ-2368
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2368
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 5.2.0, 5.3.0
>            Reporter: Mats Henrikson
>            Assignee: Rob Davies
>         Attachments: activemq-admin_reset_SUNJMX.patch
>
>
> it doesn't make any sense for activemq-admin to load the SUNJMX env var from /etc/activemq.conf since if activemq-admin is run on the same system that the broker runs on in many cases the com.sun.management.jmxremote.port system property will be set in there. Since the activemq-admin script now tries to use the same port that the broker is already using the script now fails to run.
> You could argue that there is no point for the activemq-script to even use the SUNJMX variable at all, since there is little point in enabling a JMX connector for the script.
> However in the attached patch all I've done is to reset the SUNJMX var so that it doesn't use what is set in /etc/activemq.conf.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.