[rabbitmq-discuss] debugging an unroutable message

Matthew Sackman matthew at lshift.net
Tue Mar 30 10:28:14 BST 2010

Hi Daniel,

On Mon, Mar 29, 2010 at 04:03:22AM -0400, Daniel Risacher wrote:
> Here's the bug symptom- it strictly alternates between working and not
> working.  Works the first time, not the second, etc.   When it doesn't
> work, the daemon gets the PING, but the PONG is returned as
> unroutable.

Sounds like a race between the pong being sent and the queue being
created. You're not setting the nowait option on queue.declare are you?
And you are waiting to get back the queue.declare_ok before sending the
ping? And under what conditions will the queue be deleted? Also,
(unlikely to be affecting this) is the daemon and client acking
explicitly or is noAck set? Any QoS settings?


More information about the rabbitmq-discuss mailing list