[rabbitmq-discuss] .NET client hangs on BasicGet

[Matthias Radestock]

Peter,

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 
the client.

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.


Regards,

Matthias.