[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442128#comment-16442128
]
Catalin Alexandru Zamfir commented on ARTEMIS-1285:
---------------------------------------------------
Hello,
Confirming. The Hawtio management console on the 2nd backup is the source of
these WARN-ings. The instant I've logged in to the Hawtio console for the 2nd
backup, the messages started appearing on the logs:
{code:java}
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,281 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,215 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,223 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,256 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,198 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,232 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,240 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,248 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,182 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,206 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,264 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,273 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:20:35.807 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:20:35,289 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
... here I closed the tab while writing this comment on JIRA, messages stopped
...
... the re-opened the tab. You can see that they're pritend millisecconds apart
...
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,432 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,451 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,501 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,535 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,568 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,584 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,600 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,468 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,527 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,551 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,592 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,484 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
2018-04-18 08:24:20.815 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:24:20,492 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped{code}
The instant I closed the Hawtio console tab for the 2nd backup, the message
stopped. Timestamps for proof. I've re-opened the tab/re-logged in to the
Hawtio console on the 2nd backup for a few seconds more, messages started
pouring again.
So when Hawtio console is opened, for the 2nd backup, for every Hawtio refresh,
many of these below messages are printed to the console:
{code:java}
AMQ222040: Server is stopped{code}
It is 10:30 UTC and the last messages was when I closed the Hawtio console:
{code:java}
2018-04-18 08:26:16.823 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 08:26:08,127 WARN [org.apache.activemq.artemis.core.server]
AMQ222040: Server is stopped
{code}
How should we proceed? Make a new ticket here? The message is misleading.
Tested the failover and it is working as documented (master first fail, 1st
backup fail then 2nd backup takes over).
> 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)
