Thank you very much Tim. That is enough information to get me started thinking about this. It wasn't clear to me if the brokers had separate policies or if the same policy was communicated between brokers via administrative messages.
I will almost certainly take you up on the offer of more specific questions in the future. On Wed, Aug 2, 2017 at 10:10 PM, Tim Bain <tb...@alumni.duke.edu> wrote: > There's no one-size-fits-all answer here. The basic thing to know is that > destination policies are specific to a given broker and the presence of a > given policy on one broker doesn't cause another broker to automatically > apply the same policy. > > Beyond that, how you configure each broker in an NoB depends heavily on how > that broker is being used, what its performance capabilities are, and > ultimately how you want it to behave. > > With all of that said, I'd say that more often than not you'll use the same > policies on all brokers, but that's not an across-the-board rule. > > If you have a specific policy for which you have questions about how best > to apply it in order to achieve a specific goal, please ask and we can give > a recommendation for that particular policy. > > Tim > > On Aug 2, 2017 3:12 PM, "rth" <robert.huff...@gmail.com> wrote: > > > We currently have a single broker that is configured with several > > <destinationPolicy> entries (all for topics). We will be a network of > > brokers. > > > > My question is this: how should I deal with the <destinationPolicy> > > entries? > > Do they need to be replicated across all brokers' configuration files? > > Across some subset of brokers (say, brokers from which applications will > be > > consuming the message?) Something different? > > > > > > > > > > > > -- > > View this message in context: http://activemq.2283324.n4. > > nabble.com/Network-of-brokers-and-destination-policies-tp4729188.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > >
