First make sure you are using the latest version of the broker. Second, are you using a mixture of durable subscriptions and non-durable subscriptions? If you are you might need to add a forceDurable flag to your set up. Normally the creation of a durable subscription by S on broker B should create a network durable subscription for B on broker A which would collect the messages while B is offline and then forward the messages to B when B comes back online. I just added some documentation for this on the wiki but you can also see it here: https://issues.apache.org/jira/browse/AMQ-6383
On Sat, Jan 19, 2019 at 4:15 PM carl <carl.fri...@me.com> wrote: > Hi, > > I'm having trouble with the following problem. This is my layout with a > Publisher P, Subscriber S and brokers A and B. > > P ---> A ---> B ---> S > > I need any message that P publishes to any topic to reliably reach S. I > successfully setup a durable subscription between B and S. So that covers > the case where S fails. However, when B fails, the messages published by P > in the time that B is down are lost. > > This is my network connector configuration on A: > > <networkConnector > name="T:localhost->localhost" > duplex="false" > uri="static:(tcp:/...:61616)" > userName="..." > password="..." > networkTTL="2" > dynamicOnly="false"> > <staticallyIncludedDestinations> > <topic physicalName=">"/> > </staticallyIncludedDestinations> > </networkConnector> > > Is it possible to configure the network connector so that messages are not > lost while B is down? > > Thanks for any help! > > Best, > > Carl > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
