Using the local broker as a facade for the remote broker will work, as long as it's OK for the messages from the remote broker to be stored on the local broker. (OK both from the standpoints of "allowable" and from the standpoint of having enough disk space, performance, etc.) If that isn't OK, then you need to use two entirely unconnected brokers.
Tim On May 6, 2016 1:12 PM, "Matt Pavlovich" <mattr...@gmail.com> wrote: > Allan- > > Have you looked into a store-and-forward architecture? This would allow > you to store to the local broker, then the broker would forward to the > remote broker. Same queue names, the brokers just handle everything for you. > > -Matt Pavlovich > > On 5/2/16 12:08 PM, Allan Wax wrote: > >> Is it possible to configure a broker to use a different persistence >> provider >> for a particular queue. The situation is that I have a bunch of queues >> whose persistence is on a remote broker but I want to have a vm queue >> whose >> persistence is local. If this is possible, a sample of how to do it would >> be appreciated. >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Separate-persistence-provider-per-queue-tp4711444.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > >
