Is there any way to do autorestart/manual restart of the iMQ 2.0broker?
Is there anyway to do autorestart/manual restart of the broker when
there is failure of the broker (say, the broker process is down) in case
of one broker installation?If JDBC connection (plugged-in
persistence) is used, do I need to run jmqdbmgr to maintain the
persistence before I restart the broker process?
Is it a must to use "brokers clustering" if I want to handle the failover for the broker?
We don't have anything in 2.0 to address this directly.
In 3.0 on Solaris and Linux if you pass the "-autorestart" option
to imqbrokerd (replaces jmqbroker) then it will restart the broker
if the broker fails unexpectedly.
Also in 3.0 if the broker is started via /etc/init.d/imq (from
rc3.d/S52imq) it will also restart automatically. By default the
broker is not started via S52imq. It can be configured to start
by updating /etc/imq/imqbrokerd.conf and setting AUTOSTART=TRUE
The clustering support in 2.0 and 3.0 does not support high availability.
I.e. messages published to a broker are not available until the broker
comes back up even if it is in a cluster.
