activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mats Henrikson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2368) it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf
Date Thu, 27 Aug 2009 21:39:50 GMT

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

Mats Henrikson updated AMQ-2368:
--------------------------------

    Attachment: activemq-admin_reset_SUNJMX.patch

> 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
>         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.


Mime
View raw message