SHORT SUMMARY:
Consider the following scenario:
0) Windows, JDK 7u11
1) Launch a Java application (that requires the JVM restart)
   from the command line with javaws:
   javaws https://somepath/App.jnlp
2) Take the web server hosting the Java application down / offline.
3) Again, launch the Java application from the command line with javaws:
   javaws https://somepath/App.jnlp
The Java application fails to start in offline mode if the JNLP file
is HTTPS-based. Oppositely, it starts successfully if the JNLP file
is HTTP-based (relying on the cached data).

INDICATORS:
Launch error dialog appears with the following exception:
java.lang.NullPointerException
at com.sun.deploy.security.SessionCertStore$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.security.SessionCertStore.exportState(Unknown Source)
at com.sun.deploy.util.SessionState.save(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(Thread.java:722)

TRIGGERS:
The JNLP file is referred by an HTTPS link.
The JNLP file lists some JVM parameters causing the launcher to decide to re-launch the JVM.

KNOWN WORKAROUND:
Use HTTP instead of HTTPS.

PRESENT SINCE:
No information. The problem is seen with the latest JDK 7uX updates
(7u11, 7u13).

HOW TO VERIFY:
We don't have a local testcase currently.

REGRESSION:
No information.