<div>this situation also occurs when <meta http-equiv="content-type" content="text/html; charset=utf-8">2 servers are configured both disk.</div><div>and, if the client only connects to 1 server (2 servers are clustered), no blocking is detected.</div>
<div>is that the recommended way?</div><br><br><div class="gmail_quote">2010/11/19 Liwen Fan <span dir="ltr"><<a href="mailto:f@scalethink.com">f@scalethink.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi<div> we face some blocking problems in rabbitmq cluster environment.</div><div> we have some java test clients and 2 rabbit servers clustered, one ram and the other disk, all of them are 2.1.1.</div><div> the client creates two connections when it is initialized, and holds these two connections. For each action as basicGet/basicPublish, it randomly chooses one connection.</div>
<div> the queues and exchanges are created on one server (random choose) when the client starts up.</div><div> then the client creates many threads. Each thread randomly chooses one connection and randomly chooses several exchanges to publish and several queues to get.</div>
<div><br></div>
<div> but after several message published/got, both servers face blocking problems. The test client blocks and the server command like "rabbitmqctl list_queues" and "rabbitmqctl stop" blocks too.</div>
<div> but "rabbitmqctl status" does not block and returns ok.</div><div><br></div><div> when we move to 1 single server(disk), everything turns fine. Rabbit server behaves quite well as a single node.</div><div>
</div><div> by the way, we are running on erlang R14B. Both queues and messages are persistent and durable.</div><div> Any suggestions?</div>
</blockquote></div><br>