activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holly Edelson (JIRA)" <>
Subject [jira] Commented: (AMQ-1327) Unable to rejoin a failed broker to the broker network
Date Thu, 19 Nov 2009 22:09:53 GMT


Holly Edelson commented on AMQ-1327:

I am wondering if the reproduction of this is not equal to the original error? What I mean
is, is a true broker failure testable as a broker shutdown?

> Unable to rejoin a failed broker to the broker network
> ------------------------------------------------------
>                 Key: AMQ-1327
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: Cygwin in Windows XP; JDK 1.6.0_01-b06, ActiveMQ 5.0 snapshot (rev.
>            Reporter: Kevin Su
>             Fix For: 5.4.0
> Toplogy:                
>      A network of brokers (3 or more brokers) in a star configuration, each broker interconnected
to all other brokers in the network.   
> Discovery:             
>    This problem happens with both static connection and auto-discovery through multi-cast
> Broker Conf File:  All brokers have a simple configuration as the one below: 
>     <beans>
>       <broker brokerName="sender" persistent="false" useJmx="false" xmlns="">
>         <transportConnectors>
>           <transportConnector uri="tcp://localhost:62001" />
>         </transportConnectors>
>         <networkConnectors>
>           <networkConnector uri="static:(tcp://localhost:62002,tcp://localhost:62003,tcp://localhost:62004)"/>
>         </networkConnectors>
>         <persistenceAdapter>
>           <memoryPersistenceAdapter/>
>         </persistenceAdapter>
>       </broker>
>     </beans>
> How to reproduce:
>     1. Start three brokers with names A, B, and C at port 62001, 62002, and 62003 respectively.
>     2. Kill broker C (or any of the three brokers) via CTRL-C.  Observe the other borkers
now gets into recovery mode trying to reconnect to C
>     3. Restart C.  Notice one of both of the remaining brokers (i.e. A and B) now throws
InvalidClientIDException exception.  If it does not happen the first
>         time, repeat until the exception occurs.   
> When the exception happens, C can no longer join the broker network. The only way to
recover is to shutdown and restart all three brokers.
> This does not seem to happen when there are only two brokers involved.  It happens predictably
in my environment when more then two brokers are involved.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message