My Oracle Support Banner

Java Plugin - Some Forms Client Applets Get Security Warning and Fail to Launch after Re-Signing Non-Oracle Jars with New Certificate (Doc ID 2577781.1)

Last updated on AUGUST 19, 2019

Applies to:

Java SE JDK and JRE - Version 8 to 8
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)

Symptoms

An application using embedded Forms applets (non-JNLP) experiences the following problem after re-signing its non-Oracle JAR files with a new certificate.

After the main application is launched and the user signs in, if the user tries to launch a particular Form, the Java Plugin pops up a security warning. 

If the user gives approval to run the application, the application freezes and does not respond.  The CPU usage for the process increases and the applet launch appears to be spinning in an endless loop.  The process 'jp2launcher.exe' must be killed. 

This issue happens to some Forms applets, not all.  The problem also only occurs if an affected Form is the first one launched after logging in to the application.  If a user chooses to first launch another Form that is not affected by this problem, the Form that would otherwise fail launches successfully.  Moreover, if the user closes that Form and opens an affected Form second, that Form now launches with no problem. 

If the user checks the "Do not show this again for apps from publisher and location above" option in the security warning popup, the user no longer gets the popup on subsequent uses of the Form.  This is true even if the applet failed to launch the first time and the process had to be killed.  Running the Form again is successful.  However, if the user's profile is reset, the problem occurs again if one of the affected Forms is launched first after signing in to the application. 

Note that prior to re-signing the non-Oracle JAR files, the security warning popup was not seen when launching the Forms applets.  Also note that this problem does not occur with any of the non-Oracle JAR files that were re-signed.  The Java version is the same prior to and after the JAR re-signing.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.