Details
-
Bug
-
Resolution: Duplicate
-
P3
-
6u10
-
None
-
generic
-
windows
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.
The DownloadManager initialization has to be revisited to make sure that the initialization sequence is properly implemented.
Attachments
Issue Links
- duplicates
-
JDK-6612680 Remove classloader dependency on jkernel
-
- Closed
-
- relates to
-
JDK-6833261 Error when building 6u14 b05 jkernel on Windows
-
- Resolved
-
-
JDK-6888880 JKernel VM to inject the sun.jkernel.DownloadManager as a boot classloader hook
-
- Closed
-
-
JDK-6825019 DownloadManager should not be loaded and referenced for full JRE
-
- Closed
-