<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We are performing evaluation on rabbitmq message broker, and we currently encounter difficulties with release 2.0.0:<div><br>- Our application implies 10 000 peers producing messages periodically to a unique queue. This queue is listen asynchronously by another peer.<br>- All peer are written in Java.<br>- The production rate of a single peer is 4 messages / hour.<br>- We can simulate a time-consuming task in the consumer callback, simulating more or less fast consumer.<br>- we are using SSL certificate on the broker side to allow the peer to authenticate the broker.<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- we have noticed that the use of SSL as dramatic incidence on the memory occupied by Rabbitmq process<div><br></div><div>Since we upgraded to version <b>2.0.0</b>, we are no longer able to make a test scenario running. The symptoms are listed bellow :</div></div><div><br></div><div>on the broker console first, we get the message :</div><div><br></div><div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">Erlang has closed</font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">Error: unable to connect to node rabbit@murphys: nodedown</font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">diagnostics:</font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">- nodes and their ports on murphys: [{rabbitmqctl22609,42767}]</font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">- current node: rabbitmqctl22609@murphys</font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">- current node home dir: /var/lib/rabbitmq</font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'">- current node cookie hash: qu0gh1hg7j7LKyzK0GLk+A==</font></div></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'"><br></font></div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'"><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'"><font class="Apple-style-span" face="Helvetica">we have kept the erl_crash.dump in case, but since i's about 200 MB I cannot do nothing to send it to you.</font></font></div><div style="font-family: Helvetica; ">Maybe some one can give us some hints or some indicators to look out in the dump to help diagnostics, but we are not Erlang fluent !</div><div style="font-family: Helvetica; "><br></div><div style="font-family: Helvetica; ">What we know for sure is that the crash happens while the 10 000 connections are established, at the beginning of the test. </div><div style="font-family: Helvetica; ">We have monitored the number of connections established and the crashes happens always around 4500 - 5000 connections, but never the same exact number. </div><div style="font-family: Helvetica; ">We also tried with and without SSL but this does not help at all (same symptoms).</div></font></div><div><div><br></div><div>On the client side, our application registers a ShutdownListener to implement a connection retry logic upon shutdown. </div><div>The retries always failed with the error : connection refused.</div><div><br></div><div>here are some figures we gathered during the test start up about the maximum number of connection established before it crashes </div><div><br></div><div>- with SSL : 5404, 4493, 4399</div><div><br></div><div>- without SSL : 4673</div><div><span class="Apple-tab-span" style="white-space:pre"> </span></div><div>we dont think that the problem is about file descriptors since we haven't changed anything in the configuration when we upgraded to 2.0.0.</div><div>The same test used to run successfully on previous version of the broker (1.7.2, and 1.8.1).</div><div>Moreover, the rabbit_status plugin tells us we have enough file descriptors as well as erlang processes</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- file descriptors (used / available)= 34 / 65535</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- elrang processes (used / available)= 160 / 1 000 000</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- memory (used / available)= 40 MB / 1609 MB</div><div><br></div><div>We haven't try the <b>2.1.0</b> yet because we would like to have your feedback about this issue before.</div><div><br></div><div>We would appreciate your feedbacks on that point before we migrate to release 2.1.0.</div><div><br></div><div>Best regards,</div><div><br></div><div>Romary.</div><div><br></div><div><font class="Apple-style-span" face="'Courier New'"><div style="font-family: Helvetica; "><font class="Apple-style-span" face="'Courier New'"><br></font></div></font></div></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>