-
Bug
-
Resolution: Fixed
-
P4
-
11, 13, 17, 19, 20, 21
-
b14
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8307051 | 20u-cpu | Ilarion Nakonechnyy | P4 | Resolved | Fixed | master |
| JDK-8306448 | 20.0.2 | Ilarion Nakonechnyy | P4 | Resolved | Fixed | b03 |
| JDK-8308912 | 17.0.9-oracle | Calvin Cheung | P4 | Resolved | Fixed | b01 |
| JDK-8305956 | 17.0.8 | Ilarion Nakonechnyy | P4 | Resolved | Fixed | b01 |
The issue happens in specific circumstances, when the class initialization procedure detects an error in class instantiation, tries to throw NCDFE with a correctly discovered cause (an original SOE), and catches another SOE when it tries to get the cause.
The reproducer is attached as jtreg test to the proposed fix.
Testing shows that the issue exists in versions 11, 13, 17, and 19.
- backported by
-
JDK-8305956 NoClassDefFoundError omits the original cause of an error
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8048190 NoClassDefFoundError omits original ExceptionInInitializerError
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/ce128803
-
Commit
openjdk/jdk20u/adefec35
-
Commit
openjdk/jdk/56851075
-
Review
openjdk/jdk17u-dev/1226
-
Review
openjdk/jdk20u/55
-
Review
openjdk/jdk/12566