This article explains how to properly restart JBOSS services.
Identify which node has the vip (eth0:0). Check each node with the following:
ip a
Stop processes on all JBOSS nodes Note: For Multiple Jboss nodes, it does not matter the order each node is stopped in. Though stopping the VIP node last may slightly speed up stop time.
# systemctl stop jmp-watchdog jboss jboss-dc
Note: jboss-dc is only active on VIP node, but the command won't do any harm
Confirm if JBOSS has been turned off (all jboss nodes)
# systemctl status jmp-watchdog jboss jboss-dc
Start services on the VIP node ONLY
# systemctl start jmp-watchdog
Note: watchdog starts other processes, this will take a few minutes. After 3-5 minutes you can check the webUI, or tail -F /tmp/systemStartup.log It will take a few minutes for the new version of this file to be created
Only After you can login to the Space WebUI, and after Schema has finished loading, Administration, Fabric node status. Start services on all of the other nodes
First, identify which node has the vip (eth0:0). Check each node with the following:
ifconfig eth0:0
# service jmp-watchdog stop # service jboss stop # service jboss-dc stop
# service jboss status
# service jmp-watchdog start
Note: watchdog starts other processes
After you can login to the Space WebUI, and after Schema has finished loading, Administration, Fabric node status. Start services on all of the other nodes
2024-05-28: Added 21.1 and higher version of commands (service cmd does still work)2020-02-13: Added note for clarification on waiting for first node to be up first.2020-08-26: Added note under step 1 regarding the order each node is stopped.