[
https://issues.apache.org/jira/browse/AMQ-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved AMQ-3807.
------------------------------
Resolution: Fixed
> MBeans are not unregistered under WebSphere
> -------------------------------------------
>
> Key: AMQ-3807
> URL: https://issues.apache.org/jira/browse/AMQ-3807
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMX
> Environment: WebSphere 7
> Reporter: christian ohr
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 5.7.0
>
> Attachments: ManagementContext.patch
>
>
> 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:
> {code}
> public ObjectInstance registerMBean(Object bean, ObjectName name) throws
> Exception {
> ObjectInstance result = getMBeanServer().registerMBean(bean, name);
> this.registeredMBeanNames.add(name);
> return result;
> }
> {code}
> but it should be something like:
> {code}
> 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;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
