[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442701#comment-16442701
]
Justin Bertram commented on ARTEMIS-1285:
-----------------------------------------
bq. How should we proceed? Make a new ticket here?
Yes, open a new JIRA for the issue where the broker prints {{AMQ222040: Server
is stopped}} when attempting to use the console on the 2nd back-up in a
live-backup-backup topology.
Regarding the original issue, everything you said is already understood. That's
why this issue was opened in the first place.
The documentation is part of the code-base so if there are specific things you
would like added feel free to send a pull request. Ideally if you want this
issue fixed you could send a PR for that instead. Contributions are always
welcome.
> Standby slave would not announce replication to master when the slave is down
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-1285
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1285
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.1.0
> Reporter: yangwei
> Priority: Major
>
> We have a cluster of 3 instances: A is master, B is slave and C is standby
> slave. When slave is down, we expect C announces replication to A but A is in
> standalone mode all the time. We see C waits at "nodeLocator.locateNode()"
> through jstack command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
