activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4870) Bug in the WebConsole RemoteJMX connectivity
Date Mon, 11 Nov 2013 19:01:19 GMT

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

Timothy Bish resolved AMQ-4870.
-------------------------------

       Resolution: Duplicate
    Fix Version/s: 5.10.0

Fixed on trunk. 

> Bug in the WebConsole RemoteJMX connectivity
> --------------------------------------------
>
>                 Key: AMQ-4870
>                 URL: https://issues.apache.org/jira/browse/AMQ-4870
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.8.0
>            Reporter: Joe Luo
>             Fix For: 5.10.0
>
>
> We are using a standalone ActiveMQ WebConsole that connects remotely to the broker using
JMX.
> I have noticed that a bug has been introduced by the JMX MBean naming changes that came
with ActiveMQ 5.8. It prevents the webconsole to connect to the remote broker as it doesn't
"see" the broker MBean.
> Bug affects ActiveMQ 5.8/5.9.
> Faulty code in activemq-web module in class org.apache.activemq.web.RemoteJMXBrokerFacade
> {code}
> protected Set<ObjectName> findBrokers(MBeanServerConnection connection) throws
IOException, MalformedObjectNameException {
> if (this.brokerName == null) {
>     name = new ObjectName("org.apache.activemq:type=Broker,brokerName=*");
>   } else {
>     name = new ObjectName("org.apache.activemq:brokerName="
> 					+ this.brokerName + ",Type=broker");
>   }
> ...
> {code}
> }
> When brokerName hasn't been specified, the remote JMX connection works OK.
> When the brokerName has been specified, the remote JMX connection fails.
> Fix is to replace the second name definition with the proper ObjectName :
> {code}
> name = new ObjectName("org.apache.activemq:type=Broker,brokerName=" + this.brokerName);
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message