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

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

XMLWordPrintable

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

      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.

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

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: