Do you have sample code that exhibits the problem? We use the 1.7 .net client against a 1.6 server extensively and have never run into any problems like this.<br><br>Are you properly acking your messages after your handle them?<br>
<br>Bryan<br><br><div class="gmail_quote">On Thu, Jan 14, 2010 at 6:33 AM, Peter Townsend <span dir="ltr"><<a href="mailto:Peter.Townsend@mflow.com">Peter.Townsend@mflow.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Matthias,<br>
<br>
The server logs show nothing unusual. I'm running version 1.7 broker and version 1.7 .NET client.<br>
<br>
The tracer output is attached. I've had to clean the message body content. I'll look at getting a source code version posted.<br>
<br>
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.<br>
<br>
Perhaps an issue with the message content? (binary serialized XML)<br>
<div class="im"><br>
Thanks<br>
Pete<br>
<br>
-----Original Message-----<br>
From: Matthias Radestock [mailto:<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>]<br>
</div><div class="im">Sent: 13 January 2010 20:06<br>
To: Peter Townsend<br>
Cc: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Subject: Re: [rabbitmq-discuss] .NET client hangs on BasicGet<br>
<br>
</div><div><div></div><div class="h5">Peter,<br>
<br>
Peter Townsend wrote:<br>
> Full thread dump from Managed Stack Explorer:<br>
<br>
Thanks. Looks like the client is waiting for the basic.get response.<br>
That is very odd, since the server should always send such a response. I<br>
would be amazed if there was a server-side bug here, given how heavily<br>
used basic.get is. So perhaps the response is somehow going astray in<br>
the client.<br>
<br>
Is there anything odd at all in the server logs?<br>
<br>
What version of the server and client are you running?<br>
<br>
If you have a spare few minutes, please run your test through the tracer<br>
(<a href="http://www.rabbitmq.com/examples.html#tracer" target="_blank">http://www.rabbitmq.com/examples.html#tracer</a>) and post the tracer<br>
output here (or, if it's very long, put it somewhere where I can<br>
download it). The tracer output will tell us whether client or server<br>
are doing anything strange in their interaction.<br>
<br>
Also, please post a complete (i.e. ready to compile & run) version of<br>
the code that is using BasicGet.<br>
<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</div></div><br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br>