JDK-6270512 : Print stack traces for exceptions during VM initialization
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-05-14
- Updated: 2010-07-30
- Resolved: 2005-05-26
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b38Fixed  |
Related Reports
|
Relates :
|
Description
The RMI and serialization team recently ran into a problem trying to use a ConcurrentHashMap inside of the ObjectStreamClass to speed up serialization. The ConcurrentHashMap was being allocated in the static initializer of ObjectStreamClass; this led to an exception during VM bootstrapping, and no stack trace was printed. The lack of a stack trace is problematic when working on the bootstrapping portions of the core libraries. ###@###.### 2005-05-14 01:19:27 GMT
Comments
|