JDK-8194690 : JRE bundled in App-V package will not start Java Web Start applications
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 8u131
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-01-05
  • Updated: 2018-10-16
  • Resolved: 2018-02-28
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8u172Fixed
Related Reports
Duplicate :  
JDK-8185699 - JNLP files do not open in App-V in combination with Java 8u111 and up
Relates :  
JDK-8185699 - JNLP files do not open in App-V in combination with Java 8u111 and up
Relates :  
JDK-8131070 - re enable secure launcher for cross platform launches.
Description
When using MicroSoft App-V virtualisation to sequence JRE 1.8.0_131 and create an app-v package,
apps started with the JRE in this app-v package will not start.

When JRE 1.8.0_131 is installed locally it is working fine, only under app-v is it causing issues.
Comments
Checked this in Windows 10 Enterprise (version 1709) for 8u101 b13 and 8u102 b14. Apparently the regression first seems to occur in 8u102. Confirming that the adding deployment property - "deployment.security.use.insecure.launcher=true" resolves the issue. Verified with the versions where it has failed prior (JDK 8u102 b14, JDK 8u111 b14 and JDK 162). Updated detailed results: =============== 8u101 b13: OK 8u102 b14: Fail 8u103 b02: Fail 8u111 b14: Fail 8u162: Fail 9: OK Also refer to comment in JDK-8185699 w.r.t other JDK versions.
22-02-2018
from the description in BUGDB, this could possibly be a problem in the secure launcher. It would help us to understand the problem (and possibly provide a work-around) if someone who can reproduce could try with the deployment property : deployment.security.use.insecure.launcher=true Also from related bugs we suspect this is a regression first occurring in 8u111. Would be helpful to confirm that this problem exists in 8u111 and not in 8u101
21-02-2018
need to understand how, if java is not installed (so no registration of java web start occurred), javaws could ever run. need to understand how they are invoking javaws application. first place to look is where javaws registration changed in 8u101 or 8u102. need to setup App-V package so we can determine exactly with what versions this works/doesn't work
10-01-2018