-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
after updating to 1.3.3 OWS exits without launching application #413
Comments
The original error is either with not being able to find the right classloader or failure to initialize the JVM |
java 8 does not support the --add-exports and other JVM9 module parameters and will fail if it encounters them in the command line |
Though technically correct ( which is the best kind but still), This is a new occurence. What's more, this still works with ITW and WS. So if it's java 8 we should just fall back to that behavior probably (unsupported guys are just ignored?). |
With new occurrence you mean that the program was working correctly with OWS 1.3.2? |
Yes, though I'm not 100% sure which version I had previously (but I started seeing this after updating). |
Last time we changed the behavior was with release 1.1.8 |
What you can try is to specify two JVMs in the JNLP one for 1.8* without the Java9 arguments |
I'm not sure which OWS version i had before (I tried it out a long time ago). Looks like that PR shows the issue - we used to test for Java 9+... Because JWS, ITW, and an older OWS worked with Java 8 (and a JNLP like that), it'd be great to fix that. (if it's Java 8, we should just revert to ITW's native behaviour) I can look into reworking the JNLP - my goal is to make 1.8 work across OWS, JWS, and ITW, while adding support for Java 14+ |
The behavior prior to 1.1.8 is not desirable. So we will not restore it. Rather we plan on failing explicitly when encountering modules arguments for a JVM 1.8* |
fixed in #418 |
hey all, I'm on OWS 1.3.3. I'm working on making our JNLP applications work with Oracle, ITW, and also looking into OWS (it seems this is where things are headed anyway).
My issue is that given a JNLP :
The resulting execution command is improperly made:
The log just mentions:
but if you attempt to run that command manually you'll see that it's not in the proper format...
My guess is that the add-exports et al calls create some problem when running with Java 8 -- but it should be passed after the params in that case / ignored, as the case with ITW and Oracle Java:
something like
The text was updated successfully, but these errors were encountered: