[AMQ-3807] MBeans are not unregistered under WebSphere

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.7.0
• Component/s: Broker, JMX

Environment

WebSphere 7

• Patch Info: Patch Available
• Assignee: Claus Ibsen
• Reporter: christian ohr
• Created: 16/Apr/12 07:47
• Updated: 08/Sep/12 10:56
• Resolved: 08/Sep/12 10:56

Description

When running ActiveMQ in embedded mode under WebSphere (I know that this is not a typical JEE-compliant deployment) the ObjectNames of the registered MBeans are modified by the container. Unfortunately, ActiveMQ fails to keep these names. As a result, ActiveMQ does not unregister its beans when an application is stopped, and a restart causes InstanceAlreadyExistExceptions.

The following change to ManagementContext.java may help:

Currently:

public ObjectInstance registerMBean(Object bean, ObjectName name) throws Exception {
        ObjectInstance result = getMBeanServer().registerMBean(bean, name);
        this.registeredMBeanNames.add(name);
        return result;
    }

but it should be something like:

public ObjectInstance registerMBean(Object bean, ObjectName name) throws Exception {
        ObjectInstance result = getMBeanServer().registerMBean(bean, name);
        if (result != null) this.registeredMBeanNames.add(result.getObjectName);
        return result;
    }