[
https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442092#comment-16442092
]
Catalin Alexandru Zamfir commented on ARTEMIS-1285:
---------------------------------------------------
Further information, this morning, same fresh install, the 2nd backup is not
printing 'Server not started' to logs but just 'waiting'. It's been like this
for at least 10 minutes now. Difference between yesterday and today is that I
don't have the 3 Hawtio management console open for each instance, as I need to
provide myself access (updating some FW rules to allow me to reach the 8161
port from my current location). While testing yesterday I was refreshing the
Hawtio console on the 2nd backup as soon as the instance was live. Checking and
will let you know.
Logs for the 2nd backup (r3) look like this (for now):
{code:java}
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,304 INFO [org.eclipse.jetty.server.Server] Started @6902ms
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,285 INFO [org.eclipse.jetty.server.handler.ContextHandler]
Started o.e.j.s.h.ContextHandler@32c726ee{/,file:///opt/artemis/web/,AVAILABLE}
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,284 INFO [org.eclipse.jetty.server.handler.ContextHandler]
Started
o.e.j.w.WebAppContext@e57b96d{/console,file:///var/lib/artemis/tmp/jetty-10.117.28.55-8161-console.war-_console-any-4164246465549627346.dir/webapp/,AVAILABLE}{/opt/artemis/web/console.war}
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,304 INFO [org.eclipse.jetty.server.AbstractConnector]
Started ServerConnector@39a2bb97{HTTP/1.1,[http/1.1]}{10.117.28.55:8161}
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,285 INFO [org.eclipse.jetty.server.handler.ContextHandler]
Started
o.e.j.s.h.ContextHandler@76f4b65{/,file:///var/lib/artemis/web,AVAILABLE}
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:34,921 INFO [io.hawt.system.ProxyWhitelist] Initial proxy
whitelist: [localhost, 127.0.0.1, 10.117.28.55,
i3-shared-artemis-r3-p.datalake.gameloft.org]
2018-04-18 07:56:35.635 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,312 INFO [org.apache.activemq.artemis] AMQ241001: HTTP
Server started at http://10.117.28.55:8161
2018-04-18 07:56:35.636 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p:
2018-04-18 07:56:35,313 INFO [org.apache.activemq.artemis] AMQ241004: Artemis
Console available at http://10.117.28.55:8161/console
{code}
> 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)
