640916 - Java Applet of Remote Console on HP ILO2 very slow on load and unresponsive in Firefox4+

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[gkmarty]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; cs-cz) AppleWebKit/533.20.25 (KHTML, like Gecko) Version/5.0.4 Safari/533.20.27
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0

On HP servers with ILO2 is java applet for remote console (local screen of the server).
On Firefox3 working perfect, on previous beta versions of Firefox4 working (slower, but still usable). But on Firefox4 RC1 is loading of this applet very slow with high CPU usage and it is unresponsive.

Reproducible: Always

Steps to Reproduce:
1. Open ILO2 web inerface
2. Click on "Remote Console" in menu of ILO2
3. Click on "Remote Console - Access the system KVM from a Java applet-based console requiring the availability of a JVM"
Actual Results:  
New window is opened, own process (visible in Activity Monitor) of Java applet is started which eats about 100% of cpu and same amount of memory as whole FF4. Firefox4 became unresponsive. After few minutes in window is showed java applet with message "Connecting..." and finished with message "Offline". After that, Firefox still eating more than 50% of cpu and console not working.

Expected Results:  
Same as in latest Firefox3:
New windows is opened, Java Applet correctly started within few seconds, eating < 10% of cpu and everything works flawless = remote console working.

I know reproducing of this can be very difficult, but I have no public ILO2 console accessible.
Java used in this test is the same for FF3 and FF4 (just changing Firefox).

Comment 1

[Jake Maul [:jakem]]

This still happens even in current nightlies. Affected platform seems to be Apple OSX (10.6 and 10.7, at least) with Apple Java 1.6.0_35 (current as of today... probably older versions too).

This is especially annoying because for whatever reason I'm unable to log into the iLO web console at all with Chrome or Safari... only Firefox and IE are supported. This makes iLO rather unusable from OSX altogether.


What happens to me is that I get the "do you want to trust this applet" dialog, click Trust, and then Firefox beachballs indefinitely. At first there's a spike in CPU usage by "Java Applet - <IP address>", then nothing the Firefox process becomes "Not Responding"... windows can be moved around, but I cannot interact with Firefox itself in any way. Killing the "Java Applet" process restores Firefox to full usability.

Comment 2

[Jake Maul [:jakem]]

It's worth noting that this behavior changes slightly when using Oracle/Sun Java 7 instead of Apple Java 1.6. The underlying issue appears to be the same, however.

With Sun Java, instead of a never-ending beachball, it errors out relatively quickly, indicating a class does not exist:

basic: load: class com.hp.ilo2.remcons.remcons.class not found.
Java Plug-in 1.6.0_35
Using JRE version 1.6.0_35-b10-428-11M3811 Java HotSpot(TM) 64-Bit Server VM
User home directory = /Users/jakemaul
load: class com.hp.ilo2.remcons.remcons.class not found.
java.lang.ClassNotFoundException: com.hp.ilo2.remcons.remcons.class
	at sun.plugin2.applet.Applet2ClassLoader.findClass(Applet2ClassLoader.java:252)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Plugin2ClassLoader.java:249)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Plugin2ClassLoader.java:179)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Plugin2ClassLoader.java:160)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
	at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Plugin2ClassLoader.java:690)
	at sun.plugin2.applet.Plugin2Manager.createApplet(Plugin2Manager.java:3045)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Plugin2Manager.java:1497)
	at java.lang.Thread.run(Thread.java:680)
Exception: java.lang.ClassNotFoundException: com.hp.ilo2.remcons.remcons.class

After further investigation, it turns out exactly the same thing is happening with Apple's JRE, but instead of telling you about it there's no output at all (except the errors in the console) and Firefox hangs/beachballs.

What's actually happening is that the SSL certificate used to fetch this resource has expired. In Safari and Chrome, this is not a problem... you can proceed anyway, and the app will work normally.

In Firefox, using either Apple's JRE or Oracle's, you get this error instead, possibly accompanied by the neverending-beachball-of-doom if using Apple's JRE. I will attach some more complete output from the Java Console.

Comment 3

[Jake Maul [:jakem]]

Attachment: Java console output

Comment 4

[Jake Maul [:jakem]]

Attachment: Java console output - short

Yikes, didn't realize how huge that was... here's the relevant section.

Comment 5

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

The HTML <applet> element and related java functionality was removed from Gecko in Bug 1279218. Marking related bugs as invalid.