Skip to content
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

Updating custom jvm from 8 to 13 breaks jvm #238

Closed
bskaarup opened this issue Nov 11, 2019 · 2 comments
Closed

Updating custom jvm from 8 to 13 breaks jvm #238

bskaarup opened this issue Nov 11, 2019 · 2 comments

Comments

@bskaarup
Copy link
Contributor

When moving from Java 8 to 13 (on Windows) I have found an issue that possible should be adressed.
Getdown does not clean the java_vm folder first, but perhaps it should.
In Java 8 there are 10 folders inside the lib folder. One is called "ext" (that is not present in Java 13) and it seems that the "ext" cannot coexits with Java 13. If the folder is present (even if it is empty) Java Virtual Machine Launcher crashes at startup with the message "Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit"
Deleting the folder, makes the jvm work.

The workaround I have found is to put the new jvm in a new folder (not java_vm) and set java_local_dir in getdown.txt
We use Oracle Java 8u201 and AdoptOpenJDK 13.1

@Adrodoc
Copy link

Adrodoc commented Nov 4, 2021

I think this is a duplicate of #112.

@bskaarup
Copy link
Contributor Author

Fixed with #257

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants