You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/02/01 23:54:39 UTC
[jira] [Assigned] (ARTEMIS-380) Cluster Topology is wrong after
update restart.
[ https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram reassigned ARTEMIS-380:
--------------------------------------
Assignee: Justin Bertram
> 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
>
> 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)