[rabbitmq-discuss] AMQP heartbeat - Expected behaviors

[Matt Pietrek]

Thanks Mathias and Gavin!

Just to add some additional insight into the Pika case, we're actually
using heartbeat with the BlockingConnection.

There were a couple of minor bugs I had to fix in heartbeat. py, and yes, I
hope to file bugs/pull requests.

With this added info, I can better explain the original issue. When we read
a message, we may not ack it for hours. Since there's no other activity on
the queue connection, the heartbeat.py logic never gets a chance to
execute. Eventually the server times out our connection because it's sent
frames but no Pika code gets run while we're working away.

Matt

On Tue, Jul 3, 2012 at 1:25 PM, Gavin M. Roy <gmr at myyearbook.com> wrote:

>
> On Jul 3, 2012, at 4:18 PM, Matthias Radestock wrote:
>
> > On 03/07/12 21:14, Gavin M. Roy wrote:
> >> we're sending a Heartbeat frame and expecting the response.
> >
> > Erhm. There is no response.
>
> LOL well there you go, I'm going off memory (a bit rusty memory).  In
> looking at the code, it's sending the frame on an IOLoop timer and looking
> for byte counter changes.
>
> Gavin
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> 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/20120703/0defd18e/attachment.htm>