JDK-6791692 : applet under next geneneration plug-in fails with exception
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2009-01-08
  • Updated: 2010-11-03
  • Resolved: 2009-01-30
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.
JDK 6
6u12 b04Fixed
Description
When running applet under 6u10 of the Java plug-in the following exception is encountered.  The same applet runs fine under the classic plug-in.

Below is the expection from the Java Console.
network: Connecting https://accessi3.jpmorgan.com/content/tssweb/shared/document/LB404.html with cookie "BRAND=jpma; stripeCookie=GEQ0221; TARGET_URL=https://tssportali3.jpmorgan.com/pp/pp/WSQ0221/servlet/starthomepage; SMSESSION=SOuaAGM4TinmUsSSMWUwE5SNhjRISEvmBrTQG73t/cxEOXrVtfqNjHt3A0uFw3RJWbKNAGVjGNAQHrdgZdEKa4k5W36DwHZG9QXw2bcQlAgtgSoPS98aVkvK5slOtOlOD36+joHQrs/XsUH+7996Fb/vOj8AgANxCpqctqO+Vt8VWeWU73cuiZosNdmgV9aN9j1Y5iiPol3t8HqOmqv3l/0FgVyNysqrPuprEsq+a4DhYEu4QvYiTVDI5oour1nHiPY6/dB9LIjNnLl+E+6H/Zpkjf46ncJIIf5TD9x3gObbuxorPvq0rd70S8EkIlziJdKgLaPhzGKkYhBwdFOTUJ0/+Rmat04LXih7yBBHlF6KadapIkSrGFVgk0fv7qqfCbljQwa9wlc8ih+5eM01tXCkEKzngIlcomfJ/sHLujNkYPwFDkFhctqEkOOUirf3Re7+8x4/KqNA+lxNeeF/KAM+reCtgMVb8NJm3dP9R4gShu/atwPMalaBPFoR5enJylhTbUCSAoFrtw7XYvW7IsQE58TmO7cNzP2D0IIF9AaosIY5a6dgOxu9MFW6ich/KlzZBTu379SI7dS/A8jd04cG+myurQ8qXlmpdD5vKthG7J1P1pfersI1PCR54L5YCHbE53WZ/zzrhKNmr9mb3GU8DeClvZ/MMGcdjh3E/hNlLvmMZLGhVtzVQZX4yGCwQs7JMESQkRHOGZptBmpcPR5qIB7fQUwzr2Ki6PKlZNHKkgbYJ6Z/06mz/ZE/pxFu1DcDAovf/zQ=; auth-user-info=fsiteminder3|20081211172201|20081211164449; user-cookie=fsiteminder3; nt-user-cookie=fsiteminder3; session-cookie=900; TLA=WSQ0221; JPMASSPJSESSIONID=QzmqJBSJbJNsLd7zLQyvYmDTGNFDcvQ91mQzGQqKW8VVNXy72s9v!-84824050!NONE"
basic: load: class com.jpmchase.tss.fti.client.gui.PaymentApplet.class not found.
load: class com.jpmchase.tss.fti.client.gui.PaymentApplet.class not found.
java.lang.ClassNotFoundException: com.jpmchase.tss.fti.client.gui.PaymentApplet.class
        at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
        at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
        at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Socket is closed
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(Unknown Source)
        at com.sun.net.ssl.internal.ssl.AppInputStream.available(Unknown Source)
        at java.io.BufferedInputStream.read(Unknown Source)
        at sun.net.www.MeteredStream.read(Unknown Source)
        at java.io.BufferedInputStream.fill(Unknown Source)
        at java.io.BufferedInputStream.read1(Unknown Source)
        at java.io.BufferedInputStream.read(Unknown Source)
        at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
        at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
        at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        ... 7 more
Exception: java.lang.ClassNotFoundException: com.jpmchase.tss.fti.client.gui.PaymentApplet.class
Ignored exception: java.lang.ClassNotFoundException: com.jpmchase.tss.fti.client.gui.PaymentApplet.class

Unchecking 'Enable the next-generation Java Plug-in in the Java Control Panel is not an acceptible workaround.  For the users will need to close all their browsers and relaunch.  

Oddly Enough this issue does not present itself when we are running standalone (no portal, no ssl).

Debugging was turned on and the java console output was collected.  Two logs were collected one when the next generation plug-in was enabled and one when it was disabled.  The two respective files: JRE6-Update-enabled.txt and JRE6-Update-disabled.txt are attached.

Comments
EVALUATION The new plugin class loader need to filter out invalid jar name when parse *archive* properties
15-01-2009