[rabbitmq-discuss] Intermittent Problem - 2.8.5 java client hangs on declare exchange

Fri Aug 24 16:34:41 BST 2012

We had a similar issue (I think we where running 2.6.1 or so)... the
exchange/queue declare did eventually happen (after quite a long time).
The same code run just fine on another computer (so we suspected that it
was unrelated to RabbitMQ. After having investigated the issue
for quite a while it turned out to be due to the IPv6 stack timing out (the
routing was set up the wrong way.

Just mentioning it, because it might be a similar issue...

Cheers
Maze

On Fri, Aug 24, 2012 at 4:55 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Matthew,
>
>
> On 24/08/12 15:44, m.luchak at smartasking.com wrote:
>
>> what in theory would happen if the server closed the AMQP
>> connection {inet_error,etimedout} and the client was connecting?  In
>> theory would this cause the client to hang?
>>
>
> It shouldn't, i.e. the client should see the socket close. etimedout is
> the kind of error that is indicative of network problems though, and in
> some cases these can take quite a while to be noticed by the parties.
> Configuring the clients to enable AMQP heartbeats is one way of addressing
> that problem.
>
> Regards,
>
> Matthias.
>
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120824/f0c5fbec/attachment.htm>