About the three point you have mentioned:
1, My OS is Window 7, I use system explorer to kill process every time.
2, We have done some experiments, but nothing useful.
3, If normally kill GUARD, every process works perfectly.
Finnally we choose to run ActiveMQ in a single process cause we don't ha
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
There is another weird thing:
I tried that starting ActiveMQ in a single process named AMQ, and let GUARD
watch it and restart it when AMQ exit abnormally.
In this senario, GUARD just do one thing. monitor all the other processes
and restart them if needed.
Then amazing things happen: no matter
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 th
Scenario:
I have five process: guard, watchdog, mdp, ems and security. Each process's
work is as follows:
Gurad: start an ActiveMQ server; monitor process watchdog, mdp, ems and
security, restart these process if they shutdown abnormally.
Watchdog: monitor process guard, restart it if it shutdown a
