[
https://issues.apache.org/activemq/browse/AMQ-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Strachan resolved AMQ-917.
--------------------------------
Resolution: Cannot Reproduce
am gonna mark this issue as resolved until we get a patch which works on trunk.
Let us know when you can make one and we can reopen
> Discovery Network Connector needs to clean up internal ...
> ----------------------------------------------------------
>
> Key: AMQ-917
> URL: https://issues.apache.org/activemq/browse/AMQ-917
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.0.0
> Reporter: Sridhar Komandur
> Assignee: James Strachan
> Attachments: dnc4.1patch.txt, new_patchfile.txt, patchfile.txt,
> patchfile.txt
>
>
> Consider the following scenario: All the brokers are using a directory
> service based discovery agent (for example, DNS). Broker A comes up and tries
> to connect to broker B, which is not functional yet. The Discovery Network
> Connector at A adds service B to its tracking state "bridges" (list of
> connected services) before activating the connection. However, if there is a
> failure, the data structure is not cleaned up. When the DNS Discovery Agent
> module rescans (DNS) and passes on uri for B into DNC, it simply ignores it
> (as its tracking state hasn't been cleaned up upon prior failure).
> The attached patch should take care of this issue (in the observed code path)
> - test log below:
> 2006-09-11 15:36:11,810 [main ] INFO
> network.DemandForwardingBridge1 - Starting a network connection between
> vm://localhost#0 and tcp://null:0 has been established.
> 2006-09-11 15:36:48,158 [main ] DEBUG
> network.DemandForwardingBridge1 - stopping localhost bridge to null is
> disposed already ? false
> 2006-09-11 15:36:48,158 [main ] INFO
> ransport.vm.VMTransportFactory1 - Shutting down VM connectors for broker:
> localhost
> 2006-09-11 15:36:48,159 [main ] INFO
> ransport.vm.VMTransportFactory1 - Shutting down VM connectors for broker:
> localhost
> 2006-09-11 15:36:48,162 [main ] INFO
> vemq.broker.TransportConnector1 - Connector vm://localhost Stopped
> 2006-09-11 15:36:48,162 [main ] DEBUG
> network.DemandForwardingBridge1 - localhost bridge to null stopped
> 2006-09-11 15:37:11,246 [main ] WARN
> ivemq.network.NetworkConnector1 - Could not start network bridge between:
> vm://localhost?network=true and: tcp://komandur-2.desktop.amazon.com:61617
> due to: java.net.ConnectException: Connection refused
> java.net.ConnectException: Connection refused
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
