[
https://issues.apache.org/activemq/browse/AMQ-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-1848:
----------------------------
Attachment: AMQ-1848.patch
the recieving Transportconnection that initiates the duplex network bridge on
the target broker is not stopped and hense not unregistered from JMX. Directing
the bridge stop through this connection when the bridge is duplex fixes the
problem. Test case and fix attached in this patch.
> TransportConnection MBeans leaked on duplex network connector disconnect
> ------------------------------------------------------------------------
>
> Key: AMQ-1848
> URL: https://issues.apache.org/activemq/browse/AMQ-1848
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.1.0
> Reporter: Gary Tully
> Fix For: 5.2.0
>
> Attachments: AMQ-1848.patch
>
>
> multiple restarts of a broker with a duplex network connector will result in
> multiple connection mbeans in the network target broker. These MBeans are not
> cleaned up on network disconnect.
> These leaked MBeans have names of the form:
> org.apache.activemq:BrokerName=broker,Type=Connection,ConnectorName=tcp_//localhost_61616,ViewType=address,Name=/127.0.0.1_3895
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
