Hey James, For what it's worth... You can continue using static:(failover:(uri1, uri2)) with the addition of the following query params "?randomize=false&maxReconnectAttempts=0" which is functionally equivalent to the "masterslave" protocol, e.g.: static:(failover:(uri1,uri1)?randomize=false&maxReconnectAttempts=0)
I have an outstanding PR (https://github.com/apache/activemq/pull/835) to replace the non-inclusive terminology with a new convenience transport to replace "masterslave" that would look like this: "staticfailover:(uri1,uri2)". - Lucas On 2022-10-12, 8:04 AM, "Matt Pavlovich" <mattr...@gmail.com> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hello James- First thing— You have an inconsistent url — change "static:(failover:” to uri=“masterslave:(tcp://hosta,tcp:hostb <tcp://hosta,tcp:hostb>)” .. Network Connectors imply failover and retry, and the ‘masterslave’ discovery does a connect HOSTA, then HOSTB convention. -Matt Pavlovich > On Oct 12, 2022, at 9:48 AM, James McCullough <james.mccullo...@broadcom.com.INVALID> wrote: > > Hello, > > We have a network of brokers in a hub/spoke setup > > where each client (spoke) is configured with failover to the hub (HOSTA/HOSTB) as follows: > > <networkConnector name="da_manager" uri="static:(failover:(tcp://HOSTA:61616,tcp://HOSTB:61616)?maxReconnectAttempts=3)" duplex="true" > suppressDuplicateTopicSubscriptions="false"> > > </networkConnector> > The AMQ process on HOSTB is not available, we have external processes that manage whether AMQ runs on HOSTA or HOSTB, but HOSTA and HOSTB are not both expected to be available at any one time. > > Our application relies on 2 way communication as follows: > CLIENT (producer) -> QUEUE1 -> HOSTA (consumer) > CLIENT (consumer) <- QUEUE2 <- HOSTA (producer) > > Our observation is that if the client loses contact to HOSTA for a period of time greater than 1 minute and less than 3 minutes, the client will no longer consume messages from QUEUE2, and the client broker must be restarted in order to consume messages again. > > We have tried many of the configuration options from https://activemq.apache.org/failover-transport-reference.html <https://activemq.apache.org/failover-transport-reference.html> to no avail. Is this a known issue. I am testing with AMQ 5.17.2, but have seen this issue as far back as 5.15.8 > > Any insight would be welcome. > > Regards > James McCullough > > This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
