JDK-6825019 : DownloadManager should not be loaded and referenced for full JRE
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2009-04-01
  • Updated: 2014-03-03
  • Resolved: 2010-08-04
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 7
7Fixed
Related Reports
Relates :  
JDK-6833260 - Revisit DownloadManager initialization if it should only begin after VM completes its initialization
Relates :  
JDK-6798873 - Reduce the number of classes loaded and class dependencies
Relates :  
JDK-6612680 - Remove classloader dependency on jkernel
Description
sun.jkernel.DownloadManager is only needed for Kernel JRE.

Full JRE should not need DownloadManager in any application run.  The kernel VM sets a flag indicating if the running jvm is a kernel VM (see struct jvm_version_info in jvm.h).  The JRE can use the VM interface to detect if it's in kernel JRE or not.

For FX video applet run, here is the number of invocations collected from the nb profile data:
   DownloadManager.getBootClassPathEntryForClass    1621
   DownloadManager.getBootClassPathEntryForResource 1632
   DownloadManager.isJREComplete                    1667
Comments
EVALUATION Does not seem worth to be ported back in the JRE 6.
04-08-2010
EVALUATION This likely to be dup of 6612680. On the related note while DownloadManager does not do anything useful in case of complete JRE it is unclear if these methods have any noticeable overhead. They should only check boolean value and return in case of full JRE and this likely to be inlined by JIT.
02-04-2009