You are welcome =) failover - client side to support auto-reconnect to one or more brokers due to connection drop
masterslave - broker side to support exactly your architecture. Moving messages to one of a group of brokers where there is one active and one or more failover brokers Matt Pavlovich > On Feb 28, 2024, at 12:00 AM, Bruce Cooper <br...@mechination.com.au> wrote: > > Hi Matt, > > Thank you sooo much for answering my question. That simple config change > fixed the problem! I’m so grateful > > Out of curiosity, the documentation mentions > > but there are a some other non-intuitive options that must be configured for > it to work as desired > > For my own edification, is there any explanation anywhere of the differences > between failover and masterslave? I’d be curious to understand how it works. > > Thanks again. > > > > >> On 28 Feb 2024, at 10:58 am, Matt Pavlovich <mattr...@gmail.com> wrote: >> >> Hi Bruce- >> >> Network Connectors retry or ‘failover’ automatically, so you should don’t >> use the ‘failover’ transport in your networkConnector uri. >> >> The networkConnector uri scheme you are looking for in this architecture is >> ‘masterslave’: >> >> https://activemq.apache.org/components/classic/documentation/networks-of-brokers >> >> Thanks, >> Matt Pavlovich >> >>> On Feb 22, 2024, at 8:20 PM, Bruce Cooper <br...@mechination.com.au> wrote: >>> >>> "static:failover: >> >
