Skip to content
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

'can't be called from trap context'-Error when a INT-signal is sent with Ruby >= 2.0.0 #5

Closed
philkman opened this issue Oct 22, 2014 · 0 comments
Labels

Comments

@philkman
Copy link
Contributor

If a Sig-Int is sent to the Worker-Dispatcher under Ruby >= 2.0.0, Ruby reports a 'can't be called from trap context'-Error.
It seems, that Ruby 2.0 tries to be more thread-safe and raise an exception, if something is called which could cause a deadlock.

The workaround could be, putting the problematic code (like writing to a DB or to a Log-File) inside a new thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant