The name is a little misleading, but it doesn't do what you're afraid it will. A better name would be replayToRemoteBrokerWithAtLeastOneConsumerWhenNoLocalConsumers. But most people don't like long names, so instead it's the ambiguous replayWhenNoConsumers.
Messages are still forwarded only on demand (unless you have staticallyIncludedDestinations set), but when no local consumers exist, the broker is allowed to disregard the normal rule that a message may not be sent back to a broker it's already been to. Nothing more. Tim On Dec 7, 2017 6:51 AM, "Devlin" <rbasmaj...@ofiglobal.com> wrote: > Hi Tim, > > Different hosts. > > We used conditionalNetworkBridgeFilterFactory in the past, but removed it > months ago thinking it was causing a different issue, turned out to be > false, so we are considering enabling it again. What I don't like about > this > filter is that it only kicks in on broker startup when no consumers are > active. If we set replayWhenNoConsumers="false", does the filter constantly > replay messages, irrespective of whether consumers exist or not? > > <destinationPolicy> > <policyMap> > <policyEntries> > <policyEntry queue="TEST.>" enableAudit="false"> > <conditionalNetworkBridgeFilterFactory > replayWhenNoConsumers="true"/> > </policyEntry> > </policyEntries> > </policyMap> > </destinationPolicy> > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
