| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2176810 | 7 | Karen Kinnear | P3 | Closed | Fixed | b06 |
| JDK-2171767 | 6u4 | Karen Kinnear | P3 | Closed | Fixed | b03 |
Currently, when the VM throws a NoClassDefFoundError, the details of the causative ClassNotFoundException are lost (only the detail message is preserved). NoClassDefFoundError should be retrofitted with a new constructor that takes a cause (Throwable) and passes it up to Error(Throwable). The VM should use this constructor when it throws a NoClassDefFoundError as a result of a ClassNotFoundException. This will provide a more informative stack trace. In particular, it will indicate which ClassLoader failed to find the class.
- backported by
-
JDK-2171767 NoClassDefFoundError could benefit from exception chaining
-
- Closed
-
-
-
- Closed
-
- duplicates
-
JDK-6273389 Request more diagnostic info from NoClassDefFoundError
-
- Closed
-