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 (JIRA)" <ji...@apache.org> on 2008/07/09 17:10:00 UTC
[jira] Created: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
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
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.
[jira] Commented: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
Posted by "Dave Stanley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44171#action_44171 ]
Dave Stanley commented on AMQ-1848:
-----------------------------------
Tracking..
This also resolves NPE in DemandForwardingBridge
{code}
java.lang.NullPointerException
at org.apache.activemq.network.DemandForwardingBridgeSupport.doCreateDemandSubscription(DemandForwardingBridgeSupport.java:862)
at org.apache.activemq.network.DurableConduitBridge.createDemandSubscription(DurableConduitBridge.java:98)
at org.apache.activemq.network.DemandForwardingBridgeSupport.addConsumerInfo(DemandForwardingBridgeSupport.java:845)
at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:430)
at org.apache.activemq.network.DemandForwardingBridgeSupport$2.onCommand(DemandForwardingBridgeSupport.java:154)
at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:104)
at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:143)
at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:206)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:196)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
at java.lang.Thread.run(Thread.java:619)
{code}
> 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
> Assignee: Rob Davies
> 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.
[jira] Reopened: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reopened AMQ-1848:
-----------------------------
Test case doesn't work consistenty for iterations of start/stop greater than 2
> 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
> Assignee: Rob Davies
> 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.
[jira] Closed: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully closed AMQ-1848.
---------------------------
> 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
> Assignee: Rob Davies
> 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.
[jira] Resolved: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1848.
-----------------------------
Resolution: Fixed
Fixed by revision 675484
> 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
> Assignee: Rob Davies
> 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.
[jira] Resolved: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1848.
-----------------------------
Assignee: Rob Davies
Resolution: Fixed
Patch applied in SVN revision 675314
> 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
> Assignee: Rob Davies
> 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.
[jira] Updated: (AMQ-1848) TransportConnection MBeans leaked on
duplex network connector disconnect
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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.