You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
OWS should try to download "jvms.json" during install
OWS should come with a preshipped jvms.json in order to be happy
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.
The text was updated successfully, but these errors were encountered:
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:
(I would prefer the last)
I hope I did not produce any duplicates because there are some Whitelist tickets out there.
The text was updated successfully, but these errors were encountered: