It's very hard to DEBUG all these process because GUARD will restart the process exit abnormally using JAR file.
Connection URI we use: failover:(tcp://127.0.0.1:61616?wireFormat.maxInactivityDuration=0) (It is said that the target IP must be 127.0.0.1 if PROCESSes and JMS SERVER are running on the same host, IS THIS RIGHT?) The first time GUARD is killed in STEP 2, LOG of all these four process print: 2016-02-02 08:55:19,398 WARN [org.apache.activemq.transport.failover.FailoverTransport] - Transport (tcp://127.0.0.1:61616) failed, reason: java.net.SocketException: Connection reset, attempting to automatically reconnect 2016-02-02 08:55:23,692 INFO [org.apache.activemq.transport.failover.FailoverTransport] - Successfully reconnected to tcp://QH-20151209WEVY:61616 The second time GUARD is killed in STEP 4, LOG of abnormal PROCESSes print message as usual: 2016-02-02 08:55:17,690 INFO [com.nm.server.comm.pm.ProcessManager] - send alive msg to guard. These abnormal PROCESSes haven't detected the ActiveMQ has been restarted. Thanks for replying to me. -- View this message in context: http://activemq.2283324.n4.nabble.com/Connection-lost-when-ActiveMQ-shutdown-and-restart-twice-tp4706711p4706768.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
