activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARTEMIS-380) Cluster Topology is wrong after update restart.
Date Wed, 20 Apr 2016 15:07:25 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Bertram resolved ARTEMIS-380.
------------------------------------
    Resolution: Cannot Reproduce

> 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)

Mime
View raw message