<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jean-Phillipe,<div><br></div><div>Looking at the small section of the jstack output you gave us, it appears</div><div>that this thread is still runnable, and is holding three locks.</div><div> It is doing blocking write IO to a socket, which may very well not be</div><div>doing very much (if you have run out of memory more than just in the</div><div>JVM). Just because it is there in the threads, doesn't mean it is related</div><div>to the out-of-memory problems you are seeing, though.</div><div><br></div><div>In general when out-of-memory exceptions are thrown in Java it is more</div><div>interesting to catch them (can we see these exceptions with stack?) and</div><div>then to try to track down what might have happened <i>after</i> the exception</div><div>is caught (or not), for often there is no sensible action taken, and tasks</div><div>and processes that simply abort can leave system resources (like</div><div>sockets?) in an invalid state. This, in turn, can leave (native) functions</div><div>hanging. This is pure speculation, however.</div><div><br></div><div>Since you are using the RabbitMQ Java client, it is worth pointing out</div><div>that one source of unintended memory consumption is</div><div>QueuingConsumer, which keeps all the messages it might receive</div><div>until you take them. If you don't ever take them out they stay there. </div><div>It is entirely possible to leave a reference around to the consumer</div><div>object which might mean that, even if you no longer use a particular</div><div>QueueingConsumer, it is not garbage collected later, so it retains</div><div>all the messages sent to it.</div><div><br></div><div>However, without further information, the out-of-memory conditions</div><div>cannot be further diagnosed.</div><div> Perhaps after your upgrade to the latest release you could report</div><div>back here to tell us if you are still having problems. A full jstack</div><div>attachment might be more revealing (and an exception stack for</div><div>the out-of-memory condition, might help, too).</div><div> Thanks.</div><div><div><span class="Apple-style-span" style="font-family: Georgia; ">Steve Powell</span></div><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><div style="font-family: Helvetica; "><font class="Apple-style-span" face="Georgia"><i><a href="mailto:steve@rabbitmq.com">steve@rabbitmq.com</a></i></font></div></div><div style="font-family: Helvetica; "><div><div><font class="Apple-style-span" face="Georgia" size="2"><span class="Apple-style-span" style="font-size: 10px; ">[</span><i>wrk</i><span class="Apple-style-span" style="font-size: 10px; ">: +44-2380-111-528] [</span><i>mob</i><span class="Apple-style-span" style="font-size: 10px; ">: +44-7815-838-558]</span></font></div><div style="font-size: 12px; "><font class="Apple-style-span" face="arial" size="3"><span class="Apple-style-span" style="border-collapse: collapse; font-size: 13px; "><i></i></span><i></i></font></div></div></div></span>
</div>
<br><div><div>On 9 Sep 2011, at 09:57, <<a href="mailto:jeanphilippe1.caruana@orange-ftgroup.com">jeanphilippe1.caruana@orange-ftgroup.com</a>> wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-September/014991.html">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-September/014991.html</a></font></div></blockquote></div><br></div></body></html>