[rabbitmq-discuss] Handle Stale Connections on Clients

Gary Russell grussell at vmware.com
Thu Jul 12 18:19:35 BST 2012

You'll have to catch the exception on the  *sendAndReceive() but, yes, 
it will reconnect if you try again.

There's no out-of-the-box mechanism to recycle the connection; you could 
add a connection listener to get a reference to the connection and close 
it from time to time, but this will likely impact in-flight messages.


On 07/12/2012 01:03 PM, cogitate wrote:
> Thanks Gary again for pointers!
> ** ah, so all i have to do is pool rabbit-template objects and i'll get the
> benefit of re-connecting?
> ** do you think we could have a hard reconnect after every "x" minutes so
> that if the brokers are behind a VIP and some are brought down and brought
> back up, the VIP will do fair-load-balancing?
> regards,
> -monish
> Gary Russell wrote
>> Sorry for the delay.
>> The current spring-amqp (1.1.1) now supports a 'fixed' reply queue for
>> request/reply scenarios.
>> See
>> http://static.springsource.org/spring-amqp/docs/1.1.1.RELEASE/reference/html/#request-reply
>> We added this specifically for the performance impact you cite.
>> Gary
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/Handle-Stale-Connections-on-Clients-tp20687p20761.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list