-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
DeadTaskErrors on JRuby 1.7.3 #738
Comments
Sounds like a JRuby issue. Why do you think this has anything to do with Sidekiq? |
I have no reason to think it has anything to do with Sidekiq, but if the breakage is due to an intentional change on their end, I imagine Sidekiq will be expected to conform to that rather than the other way around. I've created an issue in the JRuby project too: jruby/jruby#550 Let's see if anyone on that side has a clue what might be happening. I'll keep digging too. |
Sounds like it might also be a celluloid issue (it features pretty heavily in the stack trace, obviously): celluloid/celluloid#169 |
Definitely some compatibility issue between Celluloid and JRuby 1.7.3. I'll investigate more tonight |
This is definitely a JRuby bug: http://jira.codehaus.org/browse/JRUBY-7112 I will try to ship a workaround in Celluloid 0.13 |
ffff |
When I upgraded to JRuby 1.7.3 (from 1.7.2), I get the following errors when starting up Sidekiq 1.7.5 (sorry about the foreman output prefixing):
Sidekiq continues running, but doesn't process any jobs.
Downgrading to JRuby 1.7.2 and restarting Sidekiq immediately fixes the problem.
The text was updated successfully, but these errors were encountered: