-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.1.0.CR2
-
Release Notes
-
-
In high-availability configurations, AMQ Console is now accessible when a slave broker returns control to the master broker. Previously, AMQ Console would become unavailable for the slave broker when it gave control back to the master broker.
-
Documented as Resolved Issue
-
-
When slave goes from live back to backup, it shuts down everything. Even its own hawtio console. That should not happen. By default console is always available.
Active backup, after master when down: [root@mtoth-rhel74-5 ~]# netstat -nlp |grep java | sort tcp6 0 0 :::1099 :::* LISTEN 2449/java tcp6 0 0 172.0.0.14:1883 :::* LISTEN 2449/java tcp6 0 0 172.0.0.14:5445 :::* LISTEN 2449/java tcp6 0 0 172.0.0.14:5672 :::* LISTEN 2449/java tcp6 0 0 172.0.0.14:61613 :::* LISTEN 2449/java tcp6 0 0 172.0.0.14:61616 :::* LISTEN 2449/java tcp6 0 0 :::34259 :::* LISTEN 2449/java >> tcp6 0 0 :::8161 :::* LISTEN 2449/java udp6 0 0 231.7.7.7:9876 :::* 2449/java udp6 0 0 231.7.7.7:9876 :::* 2449/java udp6 0 0 :::56983 :::* 2449/java Giving control back to resurrected live broker [root@mtoth-rhel74-5 ~]# netstat -nlp |grep java | sort tcp6 0 0 :::1099 :::* LISTEN 2449/java tcp6 0 0 :::34259 :::* LISTEN 2449/java udp6 0 0 231.7.7.7:9876 :::* 2449/java
Observe console port 8161 being inaccessible (console goes down)
- is duplicated by
-
ENTMQBR-1200 When live-slave fails-back to master, it turns off everything down, even its console
- Closed
- is related to
-
ENTMQBR-1189 [HA-replication 1 pair] - no failback allowed, when master is killed and started again master does not connect to slave HA pair, but creates one himself
- Closed
-
ARTEMIS-1737 Loading...
- relates to
-
ENTMQBR-932 Failover to Slave Does Not Occur is Killing master with Kill -9 in a more than 2 broker cluster
- Closed