[jira] [Commented] (ARTEMIS-380) Cluster Topology is wrong after update restart.

["Justin Bertram (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127199#comment-15127199 ] 

Justin Bertram commented on ARTEMIS-380:
----------------------------------------

Thanks for the bug report!

Can you quantify your statement, "This problem doesn't show up very often"?  For example, how many times do you have to run the test before you see a failure?  The test takes around 4.5 minutes to run on my box so if we talking 100 runs to see a failure (i.e. almost 8 hours of testing) then the test needs to be re-engineered to reproduce the failure more quickly.  The Artemis test-suite has lots of clustered tests.  It would make more sense to have the test there rather than a manual Maven test.  What do you think?

> Cluster Topology is wrong after update restart.
> -----------------------------------------------
>
>                 Key: ARTEMIS-380
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-380
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Howard Nguyen
>
> Setup 4 lives, 4 backups
> See configuration:
> https://github.com/khaing211/artemis-cluster-example/tree/master/src/main/resources/activemq
> Cluster Topology thinks
> backup is active, and live is backup for each pair, meanwhile it is not.
> After the following restarts:
> 1. all backups are restarted
> 2. all backups log say "backup announced"
> 3. all lives are restarted
> 4. all lives log says "server started with node id = xxxx"
> 5. Topology check through JMX / Jolokia say that the Pair[a = backup, b = live] for each pair.
> This problem doesn't show up very often. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)