[rabbitmq-discuss] .NET client hangs on BasicGet
Peter.Townsend at mflow.com
Thu Jan 14 12:33:07 GMT 2010
The server logs show nothing unusual. I'm running version 1.7 broker and version 1.7 .NET client.
The tracer output is attached. I've had to clean the message body content. I'll look at getting a source code version posted.
I mentioned before that the consumer is hanging after the same messages each time. (As I have been reloading the same messages into the queue and reattempting the consumer run). Once the consumer passes message A it hangs. If I continue running it will soon hang after a different message B. If I reset and reload the queue and re-run the consumer it will hang after message A again.
Perhaps an issue with the message content? (binary serialized XML)
From: Matthias Radestock [mailto:matthias at lshift.net]
Sent: 13 January 2010 20:06
To: Peter Townsend
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] .NET client hangs on BasicGet
Peter Townsend wrote:
> Full thread dump from Managed Stack Explorer:
Thanks. Looks like the client is waiting for the basic.get response.
That is very odd, since the server should always send such a response. I
would be amazed if there was a server-side bug here, given how heavily
used basic.get is. So perhaps the response is somehow going astray in
Is there anything odd at all in the server logs?
What version of the server and client are you running?
If you have a spare few minutes, please run your test through the tracer
(http://www.rabbitmq.com/examples.html#tracer) and post the tracer
output here (or, if it's very long, put it somewhere where I can
download it). The tracer output will tell us whether client or server
are doing anything strange in their interaction.
Also, please post a complete (i.e. ready to compile & run) version of
the code that is using BasicGet.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the rabbitmq-discuss