-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with nanite + webrick #21
Comments
Please, paste your initializer somewhere ;) |
Here it is: http://gist.github.com/459865 |
So it did work before you did the --relock? Pretty curious about that. I'm not using a mapper inside of the web server process myself. Could you add an at_exit hook that shuts down the EM reactor explicitly? |
I cant seem to get the at_exit hook to even run properly. Seems as if the above error is preventing it to. |
Actually, when commenting out line 313 in mapper.rb (in the nanite gem install), this line: |
Could this be related to this issue around rack? |
Well I guess. If I comment out the nanite initializer the problem disappears, so its something to do with the combination nanite + webrick it seems. |
A week ago or so I did a bundle install --relock on my Rails 3 app in development which uses a nanite mapper to talk to other agents. I cant be sure if something happened back then but now I can't Control-C the rails s(webrick) process any longer so now I have to kill -9 the process every time., I get this error:
^C[2010-07-01 12:02:24] ERROR SystemExit: exit
/Library/Ruby/Gems/1.8/gems/nanite-0.4.1.17/lib/nanite/mapper.rb:313:in `exit'
Im on a Mac with Snow Leopard 10.6.4, running system ruby and rails 3 betas.
No problems when running on Thin.
The text was updated successfully, but these errors were encountered: