[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted
4:13 a.m.
[
https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin...
]
Srinivas ev commented on WFLY-11374:
------------------------------------
Hi [~mnovak], it worked. Start and stop is done as you suggested, master is able to
announce the backup.
-- start master--
./standalone.sh -c standalone-full-ha.xml -b xxx.xxx.xxx.xxx -bmanagement xxx.xxx.xxx.xxx
-Djboss.bind.address.private=xxx.xxx.xxx.xxx -Djboss.server.default.config=$JBOSS_CONFIG
-Djboss.server.log.dir=/var/log/myproject/serverlogs
-DPROJECT_CONFIG_DIR=/opt/myproject/LIVEQ/conf
-DPROJECT_DEPLOYMENT_DIR=/opt/myproject/LIVEQ/wildfly/standalone/deployments
-DPROJECT_JDK_HOME=/usr/lib/jvm/java-1.8.0-openjdk -DMYPROJECT_HOME=/opt/myproject/LIVEQ/
-u 231.73.74.75 -Djboss.messaging.group.address=231.73.74.75
-Djboss.messaging.group.port=9855 -Djboss.socket.binding.port-offset=4000
-Djboss.node.name=myperf3-LIVEQ -Djboss.hostname=myperf3
-DMYPROJECT_BIN=/opt/myproject/LIVEQ/bin -Djboss.trace.log.dir=/var/log/myproject/traces
-Djboss.logs.log.dir=/var/log/myproject/logs
kill -15 28425
./jboss-cli.sh -c --controller=135.250.138.170:13990 command=:shutdown --user=admin
--password=admin@123
2018/11/29 15:45:36,713+05:30 INFO [org.apache.activemq.artemis.core.server] (Thread-3
(ActiveMQ-client-netty-threads-2140640689)) AMQ221024: Backup server
ActiveMQServerImpl::serverUUID=eb0308d8-f3a8-11e8-ad94-3dbc7a897972 is synchronized with
live-server.
2018/11/29 15:45:38,037+05:30 INFO [org.apache.activemq.artemis.core.server] (Thread-2
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@67042056-570860242))
AMQ221031: backup announced
Master Artemis in Wildfly 10.1.0.Final is not announcing backup when
restarted
------------------------------------------------------------------------------
Key: WFLY-11374
URL: https://issues.jboss.org/browse/WFLY-11374
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.1.0.Final
Reporter: Srinivas ev
Assignee: Jeff Mesnil
Priority: Blocker
Attachments: active standalone full ha.xml, master and slave log samples on
startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log,
master-server-windows.log, master.xml, rotateserver_active.log, rotateserver_active.log,
rotateserver_backup.log, rotateserver_slave.log, slave standalone full ha.xml,
slave-server-linux.log, slave-server-windows.log, slave.xml
I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and
replication and the related configurations are done for this to work.
This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3
machine.
master in standalone-full-ha.xml - refer master.xml
slave in standalone-full-ha.xml - refer slave.xml
In the startup script, I am passing all the values for placeholders of my server host
ip's accordingly.
Test scenario -
1. Bring master up.
2. Bring slave up.
3. slave will announce the backup. (AMQ221031: backup announced).
4. Make master down.
5. Replication is success.
6. Slave is acting as master/live.
7. Make master up.
Issue - master is unable to announce the backup and starts normally as a standalone
wildfly.
This backup announcement works fine in windows and failover also works as expected.
Please let me know if anything specific required along with this details.
Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
in path - /opt/aor/${my
project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
Few logs I found which may be impacting and I am not clear -
1.2018-11-21 14:28:07,238 TRACE
[org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge] (Thread-18
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@38e819b6-2112524495))
Setting up bridge between TransportConfiguration(name=http-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-30
and ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-41],
discoveryGroupConfiguration=null]: java.lang.Exception: trace
at
org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.<init>(ClusterConnectionBridge.java:129)
at
org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.createNewRecord(ClusterConnectionImpl.java:778)
at
org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.nodeUP(ClusterConnectionImpl.java:698)
at org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:264)
at
org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
2715
days inactive
2715
days old
0 comments
1 participants
participants (1)
-
Srinivas ev (Jira)