|
Quick Lists
|
|
Bug ID:
|
6833261
|
|
Votes
|
0
|
|
Synopsis
|
Error when building 6u14 b05 jkernel on Windows
|
|
Category
|
java:other
|
|
Reported Against
|
|
|
Release Fixed
|
6u14(b05)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
1-Very High
|
|
Related Bugs
|
6833260
|
|
Submit Date
|
22-APR-2009
|
|
Description
|
Windows JRE build failed.
NeededToRun attempt=1 Exec: "C:\BUILD_AREA\jdk6_14\control\build\windows-i586\tmp\kernel\j2re-image-copy\bin\java" -verbose -Dkernel.nomerge=true -Dkernel.debug=true -Dkernel.download.url=internal-resource/ -Dkernel.background.download=false -Dkernel.deploy.debug=true -verify -Xbootclasspath/a:SplitJRE.jar -Djava.security.manager sun.kernel.DownloadTest
Error occurred during initialization of VM
java.lang.ExceptionInInitializerError
at java.io.File.deleteOnExit(Unknown Source)
at sun.jkernel.DownloadManager$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.jkernel.DownloadManager.<clinit>(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at java.lang.System.initializeSystemClass(Unknown Source)
Caused by: java.lang.NullPointerException
at java.io.DeleteOnExitHook.<clinit>(Unknown Source)
at java.io.File.deleteOnExit(Unknown Source)
at sun.jkernel.DownloadManager$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.jkernel.DownloadManager.<clinit>(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at java.lang.System.initializeSystemClass(Unknown Source)
Posted Date : 2009-04-22 22:45:26.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The DownloadManager initialization begins before the VM completes its initialization (during System.initializeSystemClass). The classes/libraries needed for VM initialization should be included in the core bundle for bootstrapping. The DownloadManager should be deferred until
This issue surfaces due to the fix for 6810254.
For 6u14 b05, we will putback a fix to workaround the existing DownloadManager initialization. The DownloadManager initialization has to be revisited for the next release (see 6833260)
Posted Date : 2009-04-22 22:45:26.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |