JDK-6689006 : Cached bad jnlp prevent applet loading
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-15
  • Updated: 2010-04-04
  • Resolved: 2008-04-17
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 6
6u10Resolved
Related Reports
Duplicate :  
JDK-6688396 - Exception getting thrown on refreshing the applets and JVM fails to start sometimes
Description
In new plugin jnlp support, when build initial LaunchDesc from initial jnlp file, it builds from cache. If a jnlp is bad, plugin will not load the applet. The bad jnlp is cached and will be used for next launch even the bad jnlp file is updated and corrected on the webserver.

There is no way to launch updated(corrected) applet unless cache is cleared.
Comments
SUGGESTED FIX Fixed in merge of CR 6688396 LaunchDesc.buildDescriptor(URL url, URL documentbase) will use the 'check for update' variant of DownloadEngine.getCachedFile() ! JNLP2Manager: Removed the notion of _initialLaunchDesc, since it is ensured to have the updated version, now.
17-04-2008
EVALUATION Well, the initial LaunchDesc is always created from the origin, i.e. network stream, or file - never from cache. The transition to cache shall be save as well, since an update check is performed. The reason for the experienced lack of update might be the unchanged classloader context. I.e. if the same client JVM is being used without clearing the classloader cache, no update will be performed. The classloader cache can be cleared by: - manual using the applet console: press 'x' - killing the client JVM - restaring the browser
16-04-2008
EVALUATION see suggested fix
16-04-2008
SUGGESTED FIX agreed
16-04-2008
SUGGESTED FIX jnlp2 manager need check updated jnlp file on webserver when there is an exception building initial LaunchDesc.
15-04-2008