[rabbitmq-discuss] RabbitMQ running at 100% CPU.
chime at mu.dk
Tue Apr 15 21:08:01 BST 2008
Thanks - wonderful - and it fits with the traces I observed.
Since we are running on Intel HW, let me know if I can help by running
stuff or reproduce the problem.
On Apr 15, 2008, at 21:44 , Matthias Radestock wrote:
> Michael Arnoldus wrote:
>> Thank you for your suggestion. There is no strace on Mac OS X, but
>> I did find a way to see what the C-program was doing (see below).
> I can now reliably reproduce the problem on a Leopard machine at our
> offices, running on a ppc platform with Erlang R12B-0 from macports
> and the latest development snapshot of rabbit.
> The results indicate that this is probably a bug in Leopard, or a
> bug in the Erlang runtime that only manifests itself on Leopard.
> The trigger appears to be a tcp client closing the socket when the
> server is in the middle of writing to its peer.
> The next step is to construct a test case that doesn't involve rabbit.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1912 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080415/df1b2bd8/attachment.bin
More information about the rabbitmq-discuss