[rabbitmq-discuss] Client connection timeout
matthew at lshift.net
Fri Mar 26 20:40:42 GMT 2010
On Fri, Mar 26, 2010 at 01:34:08PM -0500, Brendan Doyle wrote:
> Or, Erlang could have decided to try and reread the .beam file for the
> module (no idea when it decides to do that), hit the same emfile error
> and decided to die.
> I did look for the restart intensity message originally because that's what I would have expected to see, but the emfile error was the first and only error message other than connection open/close and persister logs rolling. So it was probably scenario #2 you describe. I just would have expected that to take down the whole VM if the child spec was defined with restart type permanent
Well, I'm quite sure there are a large number of variations on #2. As
far as I've seen, once you hit emfile, it's pretty difficult to recover
from it, hence our move to try and stop this type of error from
happening in the first place.
> Thanks for the info, I have seen this response from you about quite a few issues ;) but that's the way things go
Yeah, any year now it'll get merged into default...
More information about the rabbitmq-discuss