I have had this exception raised when some other unhandled exception was raised in the initialize method of a subclass of EventMachine::Connection. Check that the arity of your subclass initialize method is correct and that the initialize method is running without errors.
Usually, those errors occur in initialize or post_init. The first thing you should do is add rescue inside your callbacks to find out what actually is causing that error. Def initialize(*args) ... super rescue Exception ... end def post_init ... super rescue Exception ... end.
This is great advice, and thanks for the illustration, but it doesn't catch Troy's scenario, where the arity of #initialize is wrong. That turned out to be my problem. (Actually, I was doing the calling, not being the connection.) Probably a good answer for someone else with the same question, though.
:) – Peeja Jul 3 '10 at 3:14.
I'm new to EventMachine, so I'm not sure what this means. The program is fairly complicated, so I can't really explain everything that might have led up to it. All I need is a pointer towards what to look for.
The error doesn't seem to be documented (looking at eventmachine.rubyforge.org/).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.