[
https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132471#comment-15132471
]
Justin Bertram commented on ARTEMIS-380:
----------------------------------------
Thanks for additional clarification on the use-case, but you didn't really
address my questions. To be clear, my previous questions were:
- How many times do you have to run the test before you see a failure?
- Could you port the test to the Artemis test-suite?
Another issue related to topology updates was recently fixed via ARTEMIS-385.
Could you run your test with this update and see if it addresses the problem?
I have yet to reproduce the issue with your test.
> 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
> Assignee: Justin Bertram
> Attachments: Artemis General Practice.jpg
>
>
> 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)
