JDK-6684582 : Launcher needs improved error reporting
- Type: Bug
- Component: tools
- Sub-Component: launcher
- Affected Version: 6u10
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2008-04-04
- Updated: 2011-05-24
- Resolved: 2011-05-17
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 | JDK 7 | Other |
|---|---|---|
6u10Fixed  |
7 b27Fixed |
OpenJDK6Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
When the Java launcher fails to find the main class it reports "Could not find the main class. Program will exit." On Windows using the javaw launcher this is the only error message displayed -- there is no console window available to display a stack trace. This makes debugging Java Web Start applications (and the Java Web Start launcher itself) very difficult. The attached patch to src/share/bin/java.c (from 6u10) displays the main class name in the error message when such an error occurs.
Comments
|