<div>Thanks rob, we are using java client 2.1.0.</div><div><br></div><div>it is ok now when we bring it to 2.1.1. many thanks.</div><br><br><div class="gmail_quote">2010/11/8 rob <span dir="ltr"><<a href="mailto:rob@rabbitmq.com">rob@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5">On Mon, 8 Nov 2010 20:04:20 +0800, Liwen Fan <<a href="mailto:f@scalethink.com">f@scalethink.com</a>> wrote:<br>
> Hi,<br>
><br>
> We are running rabbit 2.1.1 with java client.<br>
> Our code is simple. Many threads share a common connection. In every<br>
> thread,<br>
> it holds its own channel.<br>
> When some threads publish/get messages to/from exchanges/queues which do<br>
> not<br>
> exist, its own channel dies.<br>
> But, the problem is, other threads that calls at<br>
connection.createChannel()<br>
> will block.<br>
><br>
> we only use channel.basicGet() and channel.basicPublish() for our<br>
message<br>
> delivery.<br>
> Any suggestions?<br>
<br>
</div></div>Did you also upgrade the Java Client to 2.1.1? There was a deadlock bug<br>
that was fixed in 2.1.1 that sounds very similar to what you describe.<br>
<font color="#888888"><br>
Rob<br>
</font></blockquote></div><br>