JDK-8201651 : Better error handling during JNLP2Manager initialisation
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 8u171
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-04-17
  • Updated: 2019-01-14
  • Resolved: 2018-04-19
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.
8u192 b01Fixed
Related Reports
Relates :  
This issue is a follow up of the following bug JDK-8200724.

Brief description of the problem reported by JDK-8200724:
During initialisation of JNLP2Manager deploy code is unable to download the JNLP file due to unsuccessful SSL connection. As a result getLaunchDesc() returns null. So the app fails with NPE when it tries to retrieve app info.

It would be good to handle this situation more properly from the deploy side, (i.e. avoid NPE and throw an appropriate exception with clear reason of failure instead).