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

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P3
    • 7
    • Affects Version/s: 6u10
    • Component/s: 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.

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

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: