You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org> on 2011/10/05 16:39:34 UTC

[jira] [Closed] (AMQ-492) Design error in MulticastDiscoveryAgent use of FailoverTransportConnector?

     [ https://issues.apache.org/jira/browse/AMQ-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-492.
----------------------------

    Resolution: Fixed

4.x broker is EOL
                
> Design error in MulticastDiscoveryAgent use of FailoverTransportConnector?
> --------------------------------------------------------------------------
>
>                 Key: AMQ-492
>                 URL: https://issues.apache.org/jira/browse/AMQ-492
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 4.0
>         Environment: w2k and linux w java 1.5
>            Reporter: Dennis Cook
>             Fix For: NEEDS_REVIEWED
>
>
> I have been trying to get my head around the multicast discovery mechanism.  In particular its use of the “FailoverTransport” class is bothering me.  The issue presented itself when viewing the DEBUG level log entries that were generated after one broker of a pair, connected using this discovery mechanism, was stopped.  The FailoverTransport went into a very tight endless loop of attempts to reconnect.
> My first thought to “tweak” the Failover properties in the network connector URI.  But alais, the uri was for the multicast not the failover.  No problem, just duplicate the failover properties on the multicast agent.  After doing so, I started to think “why is failover needed at all”  won’t the connection be reestablished when the broker returns and advertises itself again?
> Can someone comment on this issue?  Is the bug that the failover properties where not available or is the problem that failover was used at all?

--
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