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.

Sign up for GitHub

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

Jump to bottom

Work around conda-forge/openjdk-feedstock#107 #462

Open

khaeru opened this issue Oct 19, 2022 · 0 comments

Labels

Member

khaeru commented Oct 19, 2022 •

edited

Loading

JDK installed in wrong directory on Windows conda-forge/openjdk-feedstock#107 results in JAVA_HOME pointing to a location that does not exist. This occurs on Windows.
This affects ixmp.JDBCBackend when it tries to start the JVM through JPype. Java cannot be located, and there are resulting messages like "No JVM shared library file (jvm.dll) found".
This only affects ixmp if OpenJDK is installed via conda.

This issue is to track the upstream one, record mitigations, and maybe discuss adjustments.

At "No JVM shared library file (jvm.dll) found" issue and the display disorder about the web interface of "The MESSAGEix framework" message_ix#659 (comment)) one workaround was to install an older version of OpenJDK from conda-forge that is not affected by the bug.
Another work-around is probably to override the JAVA_HOME value from the conda package to point to the actual location of jvm.dll.

The text was updated successfully, but these errors were encountered:

khaeru added the backend.jdbc label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment