Listeners do not receive messages after a bit of inactivity.

[ashneyderman]

I am starting to think that there is probably something going on with the server. It looks as if it does something with the channel, while I am not looking.

just tried local rabbit and this does NOT happen with the local setup.

We do host on amazon so localhost scenario is not really what will be happening in production :-(

If anything jumps at you given this info ... I am going to go and play with the debugger as per your suggestion.

Cheers,
Alex.

[ashneyderman]

Just did a little experiment with heartbeats (set it to 60 seconds) for the connection and that worked wonders for me.

The only problem now is that I can not use auto-delete queues since server can kill the connection while instance is still running. That would be handy since a lot of our queues make sense on per-instance (consuming instance that is) basis, so queue needs to be removed on each restart of the instance. Anyhow, I should probably find a way to purge the queue before I start listening but that is a totally different question.

Gary, thanks for all your help!

Cheers,
Alex.

[Gary Russell]

Also, it is not clear what version of the amqp client and spring's rabbit jars did you use in your run? they are probably coming as transitive dependencies from spring integration which I do not use.

Yeah it's pulling in 1.1.2 and the 2.8.4 client. I used the SI app because I had it handy and just dropped in your config.

just tried local rabbit and this does NOT happen with the local setup.

Cool. Strange that it stops with Amazon - if the connection is actually broken, the consumer will reconnect, so it sounds like something else is going on.