JDK-6621786 : Running the Kernel background downloader on a complete kernel damages it
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u5
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: generic
  • Submitted: 2007-10-25
  • Updated: 2010-04-04
  • Resolved: 2007-11-07
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 :  
Description
Invoking the Kernel background downloader when the Kernel JRE is already complete causes the directory lib/bundles to be recreated.  The presence of the lib/bundles directory in a completed JRE causes certain operations to fail; for instance running the background downloader again will generate the exception:

Exception in thread "main" java.lang.NullPointerException
        at sun.jkernel.DownloadManager.getBundleNames(DownloadManager.java:468)
        at sun.jkernel.DownloadManager.performCompletionIfNeeded(DownloadManager.java:504)
        at sun.jkernel.BackgroundDownloader.doBackgroundDownloads(BackgroundDownloader.java:35)
        at sun.jkernel.BackgroundDownloader.main(BackgroundDownloader.java:172)

To reproduce this bug, run the command "java -Dkernel.background.download=false sun.jkernel.BackgroundDownloader" on a completed Kernel JRE.  The lib/bundles directory will be recreated, and the next attempt to perform a background download will display the exception above.

As part of fixing this bug, we should ensure that a spurious lib/bundles directory in a completed JRE will not cause any problems.