Thanks Tim, for the hint on failover-transport. I wasn't aware it could be used with a single-instance broker. But I tested it now, and that seems to fully solve the reconnection-problem if the broker is "bumped", which makes the whole setup easier and cleaner to fix, and more robust, of course. Very nice, thanks! :)
============================================ > From: Tim Bain <tb...@alumni.duke.edu> > Subject: Re: ActiveMQ to auto-reconnect on jdbc db-failures? > Date: Sat, 8 May 2021 08:37:50 -0500 > If clients use the failover transport ( > https://activemq.apache.org/failover-transport-reference.html), > reconnection is automatic when the broker becomes available once again. > Failover isn't just for the case where you have multiple brokers, it also > allows reconnection to a single broker, or to multiple brokers behind a > single address (load balancer, DNS name, elastic/static IP, reverse proxy, > whatever). I'd never consider running a long-lived consumer without it, and > encourage you to consider it.
