-
-
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
RuntimeException from JIT #2247
Comments
Is there a reason you still need to be on 1.7.2? It's quite old and a ton of bug fixes have landed in the 1.7.x releases since then, including an updated version of invokebinder. And there's a pretty good chance that if you do want invokedynamic support, you want the newer release. You're sort of in a "no man's land" right now. |
Thanks Kevin, I figured it was probably fixed in a new version, but just wanted to make Alex
|
The early JRuby 1.7.x releases default to using invokedynamic if run on JDK 8. JDK 6 doesn't support invokedynamic, so it would never be enabled there. If you're not using it in production, you may as well disable it in development, too. This should "fix" the problem for you until you're able to upgrade. You can disable it by adding I'm going to close this for now. If you still see an invokedynamic issue in newer 1.7.x releases, please re-open or open a new issue. Thanks! |
It is not very consistent, but once in a while I am getting a RuntimeException like this:
If I restart server, it is usually working fine.
This is my command line running on jruby-1.7.2 :
The text was updated successfully, but these errors were encountered: