Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6833260

Revisit DownloadManager initialization if it should only begin after VM completes its initialization

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • P3
    • 7
    • 6u10
    • deploy
    • None

    Description

      The current DownloadManager initialization begins before VM completes its initialization during System.initializeSystemClass is called. However, the DownloadManager's static initializer assumes that the VM initialization has completed. For example, it is using java.io.FileOutputStream.

      The DownloadManager initialization has to be revisited to make sure that the initialization sequence is properly implemented.

      Attachments

        Issue Links

          duplicates

          Enhancement - null JDK-6612680 Remove classloader dependency on jkernel

          • P2 - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-6833261 Error when building 6u14 b05 jkernel on Windows

          • P1 - Blocks development and/or testing work, production could not run.
          • Resolved

          Enhancement - null JDK-6888880 JKernel VM to inject the sun.jkernel.DownloadManager as a boot classloader hook

          • P3 - Major loss of function.
          • Closed

          Enhancement - null JDK-6825019 DownloadManager should not be loaded and referenced for full JRE

          • P3 - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              mchung Mandy Chung
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: