Re: Separate persistence provider per queue

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

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

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

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

Separate persistence provider per queue

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

Re: Configuring vm with non-vm on the same broker

Thanks. Would you provide some pointers or documentation references that tell me how to doit. -- View this message in context: http://activemq.2283324.n4.nabble.com/Configuring-vm-with-non-vm-on-the-same-broker-tp4711350p4711395.html Sent from the ActiveMQ - User mailing list archive at Nabble

Configuring vm with non-vm on the same broker

I have an existing broker with multiple queues that basically store-and-forward the messages to a single central site. I now want to introduce a new queue that only runs locally and does not get forwarded to the central site. This queue will be read locally in another thread in the application.