[AMQ-4870] Bug in the WebConsole RemoteJMX connectivity

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.8.0
• Fix Version/s: 5.10.0
• Assignee: Unassigned
• Reporter: Joe Luo
• Created: 11/Nov/13 17:58
• Updated: 11/Nov/13 19:01
• Resolved: 11/Nov/13 19:01

Description

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

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");
  }
...

}

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 :

name = new ObjectName("org.apache.activemq:type=Broker,brokerName=" + this.brokerName);

Issue Links

• duplicates: AMQ-4869 Wrong JMX object name created in RemoteJMXBrokerFacade