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

jvms.json is trying to be downloaded even if "never update JVM" is set - fails on machines with no internet #353

Closed
in-fke opened this issue Nov 12, 2020 · 2 comments · Fixed by #354

Comments

@in-fke
Copy link

in-fke commented Nov 12, 2020

We are using OWS on a machine while there is no internet, thus a locally managed JVM which was downloaded previously.
Under "JVM Settings" we set "Never update JVM".

The JNLP launch fails because OWS still tries to download (the first?) "jvms.json".

Workaround:
"Pre-Fetch" jvms.json in some way, while in the internet, then go back to VPN Dial-In and go the actual launch

Suggestions:

  1. OWS should try to download "jvms.json" during install
  2. OWS should come with a preshipped jvms.json in order to be happy
  3. OWS should really honor "Never update JVM" and be happy with a manually installed JVM

(I would prefer the last)
I hope I did not produce any duplicates because there are some Whitelist tickets out there.

@sclassen
Copy link
Member

Could you give us the stacktrace from the logs so we can make sure that we do not miss the case you are encountering

@in-fke
Copy link
Author

in-fke commented Nov 12, 2020

I will try to reproduce it, but it should go as follows:

  1. Vanilla install
  2. Install one JVM manually
  3. Turn JVM Management / Settings / to "Never update JVM"
  4. turn off internet
  5. run a JNLP Launch (e.g. within the LAN, or to localhost)
  6. OWS tries and fails to download jvms.json

@sclassen sclassen linked a pull request Nov 12, 2020 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants