-
Notifications
You must be signed in to change notification settings - Fork 84
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
adapt run-java-sh to adopt the auto-generation options for Java 11 #191
Comments
I don't think it's too surprising that run-java.sh still works, but some of the things it's doing (like calculating default memory settings) shouldn't be needed any more with Java 11. |
Already created a PR for this: fabric8io-images/run-java-sh#73 which is still not merged. |
#213 is a case where Java 11 breaks with the current script. |
#214 is the PR which includes the update to run-java with the fix for Java 11 included. |
Not sure either ;) I think if we have #213 done, we can close this issue, too. |
With JDK-8146115 all of the size detection should be done automatically by the JVM. That includes JDK 8 (u191) and JDK 11. The relevant options are I cannot comment on other options those scripts use. |
@jerboaa thanks for the feedback. Actually, we should update run-java.sh either to detect also whether a Java 8 JDK supports the cgroup awareness automatically (and switch off the homegrown calculation in this case), or add an extra flag/env var to indicate that this is not needed anymore. The latter is probably is simpler (and then could be reused here when we are using the proper base image), but we might strive for the former, too. Regardless what, works needs to be done over there in ghttps://github.com/fabric8io-images/run-java-sh |
@rhuss said in #160 that, quote:
But somewhat to my surprise, I seem to actually have been able to get a (basic) Java 11 working without touching run-java-sh ... I therefore propose that we work incrementally, and get #160 wrapped up and merged, and then iterate to improve things re. the point raised above under this issue.
The text was updated successfully, but these errors were encountered: