JDK-8037471 : The warning message displays the app name and publisher as "UNKNOWN" if cache is disabled
- Type: Bug
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 6u71
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-03-14
- Updated: 2015-07-15
- Resolved: 2014-07-16
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 | JDK 8 | JDK 9 |
|---|---|---|---|
| 6u91Fixed | 7u76Fixed  |
8u31Fixed |
9 b26Fixed |
Description
A warning is displayed when the first liveconnect call is made. The warning message displays the application name and publisher as "UNKNOWN", even though these values are specified in the jar. The warning message is displayed on the first liveconnect call to the applet, within a single jvm. So, each time the user closes their browser (or if the jvm closes itself), they get the warning again. They are unable to "accept always". There are no security settings in Java 6 to change this behavior. An exception is displayed in the java console: java.lang.NullPointerException
Comments
|