JDK-8157657 : Regression: Java Web Start (javaws) 11.92 completely broken
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 8u92
  • Priority: P3
  • Status: Closed
  • Resolution: Incomplete
  • OS: linux
  • CPU: x86
  • Submitted: 2016-05-10
  • Updated: 2016-05-24
  • Resolved: 2016-05-24
Related Reports
Relates :  
Description
FULL PRODUCT VERSION :
Java(TM) Web Start 11.92.2.14-fcs

ADDITIONAL OS VERSION INFORMATION :
Windows 7 (32 bit & 64 bit)

A DESCRIPTION OF THE PROBLEM :
A Java Web Start application can no longer be started. On Linux, it can be started by disabling the Java cache. On Windows, the Java cache cannot be disabled, because the application uses a native lib (Java/COM Object Bridge aka JACOB). Native libs need the cache to function.

This may be related to bug #8155226: https://bugs.openjdk.java.net/browse/JDK-8155226

However, that bug does not mention native libs.

The Java application starts normally, when Java Web Start 11.77 (Java 1.8.0_77) is used.

REGRESSION.  Last worked in version 8u77

ADDITIONAL REGRESSION INFORMATION: 
Java(TM) Web Start 11.77.2.03-fcs

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
This is an in-house application. However, any Java application with native libs, started via Java Web Start 11.92, will probably do to reproduce this. Also note that the application in question uses additional JNLP files in a sub folder "lib".

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The Java application starts normally.
ACTUAL -
Java Web Start exits abruptly. If the cache is disabled, there is a notification that native libs cannot be used when the cache is disabled.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
There is no known workaround. The application can no longer be invoked via Java Web Start 11.92 (Java 1.8.0_92) on Windows.


Comments
Closing this as incomplete as we don't have enough information or a use case to evaluate this further. If we receive any further information from the submitter, may reopen this report.
24-05-2016

This looks similar to JDK-8155076 where the JAR file with relative path is being downloaded by the incorrect relative path containing an extra 'lib' dircetory. Moving this up for dev. confirmation.
24-05-2016