Java exceptions raised in fibers cause the fiber to die without notifying parent #1106
If a Java exception is raised in a fiber body, it will cause the fiber to terminate, leaving any resuming thread hanging on a queue pop that will never be fulfilled. The issue is in the handling of exceptions in the thread logic; Ruby exceptions propagate to the parent but Java exceptions do not, and simply terminate the thread.
This is a local fix I am testing now: https://gist.github.com/6907734
The text was updated successfully, but these errors were encountered:
Only Ruby exceptions were propagating before. This modifies the thread logic for fibers to also propaate the original Java exception out in the same way. This also allows Thread#raise to be called with a Java exception, which was missing before and needed for this fix.