Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Message-ID: <6267179.1146494918477.JavaMail.jira@brutus>
Date: Mon, 1 May 2006 14:48:38 +0000 (GMT+00:00)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Updated: (AMQ-492) Design error in MulticastDiscoveryAgent
 use of FailoverTransportConnector?
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

     [ https://issues.apache.org/activemq/browse/AMQ-492?page=3Dall ]

Hiram Chirino updated AMQ-492:
------------------------------

    Fix Version: 4.0 RC4
                     (was: 4.0)

> Design error in MulticastDiscoveryAgent use of FailoverTransportConnector=
?
> -------------------------------------------------------------------------=
-
>
>          Key: AMQ-492
>          URL: https://issues.apache.org/activemq/browse/AMQ-492
>      Project: ActiveMQ
>         Type: Bug

>   Components: Connector
>     Versions: 4.0
>  Environment: w2k and linux w java 1.5
>     Reporter: Dennis Cook
>     Assignee: Hiram Chirino
>      Fix For: 4.0 RC4

>
>
> I have been trying to get my head around the multicast discovery mechanis=
m.  In particular its use of the =93FailoverTransport=94 class is bothering=
 me.  The issue presented itself when viewing the DEBUG level log entries t=
hat were generated after one broker of a pair, connected using this discove=
ry mechanism, was stopped.  The FailoverTransport went into a very tight en=
dless loop of attempts to reconnect.
> My first thought to =93tweak=94 the Failover properties in the network co=
nnector URI.  But alais, the uri was for the multicast not the failover.  N=
o problem, just duplicate the failover properties on the multicast agent.  =
After doing so, I started to think =93why is failover needed at all=94  won=
=92t the connection be reestablished when the broker returns and advertises=
 itself again?
> Can someone comment on this issue?  Is the bug that the failover properti=
es where not available or is the problem that failover was used at all?

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira