FULL PRODUCT VERSION :
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows 7 Ultimate 64bit
Microsoft Windows [Version 6.1.7601]
A DESCRIPTION OF THE PROBLEM :
Sorry that I have to open a new bug-report but we having currently the same problem like described in this links
https://bugs.openjdk.java.net/browse/JDK-8064358
https://community.oracle.com/thread/3682142
We are getting sometimes NullPointerException when we try to start our application.
All our JARs are signed and our main-jar contains an jnlp-Template.
In most cases the start works as expected but sometimes we get the mentioned NullPointerException.
java.lang.NullPointerException
at com.sun.javaws.JnlpxArgs.execProgram(Unknown Source)
at com.sun.javaws.Launcher.relaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareResources(Unknown Source)
at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main.access$000(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
The web-start error is always:
Cannot use secure launcher with main class: XXX
where XXX is a random text from the jnlp (property, attribute etc.).
The behavior is very strange and seems to be only an issue if the jnlp was downloaded.
I'm working an a windows 7 machine with google chrome and always have to download the jnlp.
After I've downloaded the jnlp I start the local file.
In Internet Explorer I have the option to run the jnlp directly (nut sure if a temp-file is created or javaws is called with the url).
But it seems that starting from IE the NullPointerException does not occur.
Maybe you can send me the source of deploy.jar or deploy.jar with debug-informations to create a stacktrace with linenumbers.
In my opinion there is a bug on getting the class-name of the main-class.
REPRODUCIBILITY :
This bug can be reproduced often.