You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/05 23:14:29 UTC
[jira] [Resolved] (AMQ-3523) NetworkConnector MBean unregistration
can fail with a transport disconnect - leaving dangling mbean
[ https://issues.apache.org/jira/browse/AMQ-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3523.
-----------------------------
Resolution: Fixed
fixed with http://svn.apache.org/viewvc?rev=1179355&view=rev
> NetworkConnector MBean unregistration can fail with a transport disconnect - leaving dangling mbean
> ---------------------------------------------------------------------------------------------------
>
> Key: AMQ-3523
> URL: https://issues.apache.org/jira/browse/AMQ-3523
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMX
> Affects Versions: 5.5.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: jmx, networkConnector
> Fix For: 5.6.0
>
>
> MBeans for NetworkConnectors embed the target address, but on unregistraton due to shutdown from a transport failure, the remote address can be null, resulting in a failure to find the MBean. The mbean name should be remembered from registration rather than generated on the fly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira