[
https://issues.apache.org/jira/browse/AMQ-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266254#comment-17266254
]
Matt Pavlovich commented on AMQ-2725:
-------------------------------------
stop() on various top-level components should not necessarily unregister from
JMX-- networkConnector, transportConnector. Sub-instances should be transient
(ie.. networkBridge)
> Issues With NetworkConnector and NetworkBridge MBeans
> ------------------------------------------------------
>
> Key: AMQ-2725
> URL: https://issues.apache.org/jira/browse/AMQ-2725
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMX
> Affects Versions: 5.3.1
> Environment: ActiveMQ 5.3.1 on Windoze XP Pro SP2
> Reporter: Joe Francis
> Assignee: Matt Pavlovich
> Priority: Minor
> Fix For: 5.17.0
>
>
> On the JConsole, when you invoke the 'Stop' operation on the
> NetworkConnectorView MBean, the corresponding NetworkBridgeView MBean
> disappears as expected; however, when you invoke the NetworkConnectorView's
> 'Start' operation to restart the bridge, the corresponding NetworkBridgeView
> MBean does not reappear.
> When you invoke the NetworkBridgeView MBean's Stop operation, the MBean
> disappears. So there is no point having a Start operation for this MBean.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
