-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Java exceptions do not propagate out of Thread#join #2354
Comments
This logic is pretty messy and needs a rework. Here is a partial, not-compiling attempt at a patch that may be along the right lines for fixing this bug: https://gist.github.com/headius/e87a4723d643cfd38769 |
I'm pretty sure I've experienced this behavior when working with native Java libraries, going to see if I can convince @mkristian to fix it :D |
This fixes an issue where java execptions did not propogate up in Thread#join. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Fixes an issue where Java exceptions did not propogate up in Thread#join and could result in issues getting dropped. See related issue for more information: jruby/jruby#2354
Any update on this? I can still see this happening and causing weird issues |
This turned out to be easier to fix than it used to be, so I went ahead with it. Java exceptions that bubble out of Ruby threads will now behave like Ruby threads as regards Thread#join, Thread#value, and other exception-aware methods of Thread. |
From http://jira.codehaus.org/browse/JRUBY-7129
Joining a thread that died from a normal Ruby error will kill the parent thread, as expected. The "should not be here" text is never printed:
However, if the thread died from a raw Java error, joining the thread only prints a trace, and the "should not be here" text is printed.
Still fails on 1.7 and 9k heads.
The text was updated successfully, but these errors were encountered: