[rabbitmq-discuss] configure external data store(like database) for message durability in rabbitmq

PATAR, SAGAR sp345s at att.com
Tue Oct 1 15:37:58 BST 2013


Thanks Michael ..

Looks like mirrored queues will work for us ..
I was wondering if the rabbitmq-java-client--3.1.5 has the capability to seamlessly connect to the cluster in case of failovers to Slaves or masters ?? or do we have to wrap the reconnect logic ..

For multiple hosts and port .. can we use the below amqp URL ...

amqp://username1:[email protected]:portNumber1,hostname2:portNumber2,hostname3:portname4/virtualHost
                                                                   __________________________________________________________

ConnectionFactory factory = new ConnectionFactory();
 factory.setUri("amqp://username1:[email protected]:portNumber1,hostname2:portNumber2,hostname3:portname4/virtualHost");
 Connection conn = factory.newConnection();
 Channel channel = conn.createChannel().,.

Also appreciate if we can get some links to java client tutorial connecting to clustered env  , Also the spring integration ...


-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Michael Klishin
Sent: Monday, September 30, 2013 11:42 AM
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] configure external data store(like database) for message durability in rabbitmq

On sep 30, 2013, at 7:37 p.m., "PATAR, SAGAR" <sp345s at att.com> wrote:

> My assumption is when we have a file store for message durability and if one of the node goes down in the cluster the messages not been consumed yet must have been stored in that node file system and will stay till the node is back up ... those message will not be accessible by other active nodes in the cluster because the file store for that node is not accessible to other nodes....and the messages will be delayed ...
> 
> I am not sure how this scenario is handled ...seems to be a common problem

Using mirrored queues or asynchronous replication (using Shovel or Federation plugins).

See

http://www.rabbitmq.com/distributed.html
http://www.rabbitmq.com/clustering.html
http://www.rabbitmq.com/ha.html

MK





More information about the rabbitmq-discuss mailing list