[rabbitmq-discuss] RabbitMQ running at 100% CPU.

Matthias Radestock matthias at lshift.net
Tue Apr 15 22:06:35 BST 2008


Martin Sustrik wrote:
> I'm not sure whether this will help, but anyway: Leopard (and presumably 
> OS X in general) handles connection closed by the other peer by 
> returning POLLHUP from the poll rather than POLLIN as is common on most 
> platforms. Can that confuse Erlang/Rabbit?

That is certainly worth looking into since a misdiagnosis of the event 
might cause the Erlang runtime to think the socket is ready for 
reading/writing when it fact it has been closed by the peer. Thanks for 
the pointer!


More information about the rabbitmq-discuss mailing list