[rabbitmq-discuss] RabbitMQ Subscriber Timeout When Waiting for Delivery

[Steve Powell]

Dwayne,

AFAIK RabbitMQ doesn't perform any connection timeout processing, but if
your subscriber does nothing for some time the connection has been known
to be dropped by pieces of soft/hardware in the network infrastructure
you are using. In other words, if there is no traffic, some piece of
network hardware can drop you without warning. 300 seconds sounds about
right for this sort of thing.

The heartbeat mechanism can be used to fool the intervening wires that
they are being used, and thus stay open. Heartbeat overhead is
relatively low.

Steve Powell
steve at rabbitmq.com
[wrk: +44-2380-111-528] [mob: +44-7815-838-558]

On 30 Jun 2012, at 03:24, Deelo55 wrote:

> Hi,
> There is no exception or message visible. If the subscriber doesn't receive
> anything in 300 seconds it stops subscribing. I managed to solve by using a
> heartbeat. I suspect this may have something to do with the fact it is using
> an auto delete queue. Still debugging further v
> Thxs. 
> 
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-Subscriber-Timeout-When-Waiting-for-Delivery-tp20442p20464.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