Re: Separate persistence provider per queue

2016-05-06 Thread Allan Wax
Thanks for the info. I have decided to go with a separae broker. It'll be easier than a more complex setup. -- View this message in context: http://activemq.2283324.n4.nabble.com/Separate-persistence-provider-per-queue-tp4711444p4711713.html Sent from the ActiveMQ - User mailing list archive

Re: Separate persistence provider per queue

2016-05-06 Thread Allan Wax
Actually, if you read the rest of the posts, I'm trying to do the exact opposite. Not store and forward but just persist locally on the machine separate from the other store and forward queues that forward to another host. Store and forward to the same machine makes no sense to me. -- View thi

Re: Separate persistence provider per queue

2016-05-06 Thread Tim Bain
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, t

Re: Separate persistence provider per queue

2016-05-06 Thread Matt Pavlovich
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 possi

Re: Separate persistence provider per queue

2016-05-04 Thread Allan Wax
Thanks for the info. The reason for doing it this way is that the information must stay local to the machine and has nothing to do with the other queues. The persistence is needed in case the local processing that goes elsewhere on the machine fails and we need to recover later. I'm trying hard

Re: Separate persistence provider per queue

2016-05-04 Thread Tim Bain
I agree, from my very quick search it doesn't look like there's a way to do what you want. Would you really want to, even if you could? I assume the network share is to allow this broker to be part of a master-slave grouping. If one queue is persisted to a location the others can't access, then

Re: Separate persistence provider per queue

2016-05-03 Thread Allan Wax
To be clear, this is with ActiveMQ 5.x. The setup is that there is a single broker on a particular host whose purpose is to forward on messages from several queues to another host which is shared by multiple other hosts. The dataDirectory for the broker is a network location which is shared by mu

Re: Separate persistence provider per queue

2016-05-02 Thread Tim Bain
What does it mean (to you) for a queue's persistence to be local or to be on a remote broker? Those phrases don't mean anything to me, so unless they mean something to someone else, your question's unlikely to get answered as it's currently written. Please clarify what you mean, and someone may b