I have a java web start application, that I try to start via
javaws.exe https://localhost:8888/myApplication/myApplication.jnlp
nothing happens (no error message; I see no process starting in the task list).
If I start it via
javaws.exe -verbose https://localhost:8888/myApplication/myApplication.jnlp
the application starts.
I can also start the application when using
javaws.exe -viewer https://localhost:8888/myApplication/myApplication.jnlp
and then starting the application from the java cache viewer.
What is the difference, that might trigger the application to run, when in verbose mode or via the viewer? Here is my jnlp file:
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="https://localhost:8888/myApplication" href="myApplication.jnlp">
<information>
....
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.8.0_60+" href="http://java.sun.com/products/autodl/j2se" max-heap-size="500m" initial-heap-size="250m"/>
<!-- some jars are referenced -->
<property name="sun.java2d.d3d" value="false" />
</resources>
<resources os="Windows">
<nativelib href="mylib.jar" download="eager" />
</resources>
<application-desc main-class="myClass">
<argument>-initLogging</argument>
<argument>SETPROPERTYjavax.net.ssl.trustStore</argument>
<argument>_UNDEFINED_</argument>
<argument>SETPROPERTYjavax.net.ssl.trustStoreType</argument>
<argument>_UNDEFINED_</argument>
<argument>SETPROPERTYjavax.net.ssl.trustStorePassword</argument>
<argument>_UNDEFINED_</argument>
<argument>-locale</argument>
<argument>_UNDEFINED_</argument>
<argument>-serviceHost</argument>
<argument>_UNDEFINED_</argument>
<argument>-serviceProtocol</argument>
<argument>_UNDEFINED_</argument>
<argument>-servicePort</argument>
<argument>_UNDEFINED_</argument>
<argument>-trustStrategy</argument>
<argument>_UNDEFINED_</argument>
</application-desc>
</jnlp>
I had the problem, too (see my comment My java web start application only starts when verbose is set)
I solved this problem by updating Java, i.e. reinstalling Java. The file C:\ProgramData\Oracle\Java\java.settings.cfg
was created again and this new java installation could open web start applications again correctly. Although older versions still had the same bug.