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
Cannot start cerebro with the bundled JVM from ES v7.13 #514
Comments
cerebro was set up this way in the container:
|
I can verify that the solution mentioned in google/guice#1133 (comment) (thanks to @erikyao) resolves the above error:
Should this JVM option be part of |
sratz
added a commit
to sratz/cerebro
that referenced
this issue
Nov 24, 2021
Libaray com.typesafe.play / play-guice currently depends on version 4.2.3 of Guice. Guice 4.x causes 'illegal reflective access' warnings on Java 15 and prevents Cerebro from being usable with Java 16 and and 17 due to InaccessibleObjectExceptions. Explicitly include higher version 5.0.1 of the dependencies com.google.inject / guice com.google.inject.extensions / guice-assistedinject which work correctly with Java 15 and higher. Fixes lmenezes#514.
This was referenced Jan 28, 2022
I had to open another module/package
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tried to install the latest cerebro v0.9.4 in a docker container, together with ES v7.13, but got this error when start cerebro (no default-jdk installed, tried to use the bundled JVM from ES v7.13):
Note that the bundled JVM is version 16. I saw
bin/cerebro
script checksbundled_jvm
variable, not sure if it is designed for using ES bundled JVM.Same error with the setting of
JAVA_HOME
as suggested in #362.The text was updated successfully, but these errors were encountered: