Karakun Support Forums

> How come I can't access this parameter when running OWS. If I deploy from Eclipse the parameter is accessible. I've added a print out in the OWS-log so I can see that the parameter is set. > OWS runs the app in a sandbox with restricted access. > Row 66-69 in the OWS2.txt is from the application, ...

Please talk to the vendor if possible. It should not be difficult to migrate an applet to an application.

You are trying to run an applet : <applet-desc ...> as specified in your jnlp file .

Log file has: [ITW-CORE][2024-08-22 14:12:41.057 EDT][DEBUG][net.sourceforge.jnlp.Launcher] Launching Applet

OWS does not support applets.

You will have to convert your applet to a Java Application.

Which version of OWS are you using? Can you please attach the OWS logs? Which JREhave you specified in your Jnlp file to run the application?

Please see https://openwebstart.com/docs/OWSGuide. ... management.

Please make sure that you have chosen the right JVM download/update strategy.

You can control JVM choices using itw-settings > JVM Manager > Settings. Please see https://openwebstart.com/docs/OWSGuide. ... management

You can add appropriate --add-modules jvm args in the jnlp file to be able to run your application with Java 11. You can specify which JVM you want to use to run your application in the jnlp file and in the itw-settings.

OWS is starting your jnlp app by invoking the main method of your app. There are exceptions in your app:: ITW-APP ][2024-06-26 07:36:16.224 MST][ERROR][java.base/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:233)] Jun 26, 2024 7:36:16 AM com.sun.enterprise.v3.server.CommonClassLoaderService...

Please attach the OWS stage1 and stage 2 log files from the time you run you run your jnlp with OWS. Please do not copy log from console to post here.

The stack trace is not from OWS. Please post OWS logs.

Please see viewtopic.php?t=8526

Can you please post the OWS logs. See https://openwebstart.com/docs/OWSGuide.html#_logging.

We are happy to announce the release of OpenWebStart v1.10.1.

https://github.com/karakun/OpenWebStart/releases

- OpenWebStart Team at Karakun

Can you try by setting the console to Disable?

From which version of RedHat OpenJDK did you use javaws?

Which version of JVM did you use to run the Jnlp application?

What is your OWS Logging > Log Console setting? Is it Show? OWS runs in two stages. Firstly it starts itself with the bundled JRE and processes the Jnlp file, especially for the Java version specified in it. Then it starts the second stage with the JVM that matches the JVM specified in the Jnlp file...

This is a bug. We will fix it and make a new release soon. For now you can use the following workaround: In your deployment.properties file please specify the following property: ows.jvmargs.for.<name_of_your_jnlp>=-D<propName1>=<propValue1> -D<propName2>=<propValue2> So if the name of your jnlp fil...

I could reproduce. I will investigate and come back. Thanks for pointing to the issue.

https://openwebstart.com/docs/OWSGuide. ... figuration

https://openwebstart.com/docs/OWSGuide. ... stallation

Using the itw-settings app > JVM Manager > settings, you can choose the Java Update Strategy. The chosen strategy will be captured in deployment.properties file. The property ows.jvm.manager.updateStrategy can then be copied to response.varfile. It will be copied to the deployment.properties file up...

For OWS Auto update Options:

itw-settings > Updates

For Java update options

itw-settings > JVM Manager > Settings > Update strategy dropdown.

I am sorry I do not understand your issue. Please consider buying support https://openwebstart.com/support/