Karakun Support Forums

see also: https://github.com/karakun/OpenWebStart/issues/412

Yes, we did not have time to document all the flags and features.

The default for deployment.security.level is ASK_UNSIGNED which is equivalent to HIGH in the oracle settings.

Thank you for reporting this. We have fixed the documentation.

Sorry, so far we did not find the time to document all features and flags which are available in ITW and OWS.
If you need to know more details about anything please feel free to ask

deployment.console.startup.mode=SHOW

You need to put the above line into the file "deployment.properties" in the folder "%user_home%\.config\icedtea-web"

Hi Amitabha

Yes this is the expected behavior.
If you want to reset your config to default you need to delete the deployment.properties file.
This file is located in your users home dir below ".config/icedtea-web"

According to https://github.com/AdoptOpenJDK/openjdk ... ssues/1254 TLS 1.3 support was added in 8u272.
The OWS version 1.4.0 will contain an updated JRE which should contain TLS 1.3 support.
Release is planned for April 2021.

Can you share the JNLP with us. The error suggests that either a the native lib is not found or the method which the java code is trying to invoke cannot be found. There are two likely causes. JavaFX is not referenced correctly in the JNLP (hence we want to take a look at that file) Or you have an i...

Sorry so far there is no such option.
Mainly because for some application it is ok if not all the resources are available.

Yes this is currently missing.
We will add this property with the next release of OWS

Yes, OpenWebStart does no longer support applets.
You will need to convert the your applet to an application.

In the deployment.properties (per user or system wide) you can add the following line:

deployment.security.level=ALLOW_UNSIGNED

This will disable a series of security checks including the one causing the warning you see

You can safe the decision by selecting the checkbox on the very bottom of the dialog.

I don't think downgrading is the solution. But I am kind of running out of ideas.

Just to state the obvious:
Can you check that the file /usr/lib/jvm/java-1.8.0-amazon-corretto/jre/lib/amd64/libglassgtk3.so exists and is readable by the user which is starting the JNLP

Can you start the application locally (without webstart) using the exact same JVM (/usr/lib/jvm/java-1.8.0-amazon-corretto/bin/java)
JavaFX and JVM 1.8.0 with a bugfix version greater than 200 (in your case this is 282) are known to have problems

Also when you enable log to file there are always 2 log files created. "stage1" and "stage2".
In the stage1 log file you can find the command which is used to launch stage2. This command includes the path to the JVM for stage 2 so you can make sure that expected/required JVM is used.

There is a dedicated JVM with OpenWebStart. It is located in "/opt/OpenWebStart/jre"
Is it missing on your machine?

Can you please retry with 1.3.2

please retry with version 1.3.2

Sorry have not yet found the time to discuss this.