Hello,

I have just tested this out with HEAD, I do not get the above mentioned error, and it does not load with Sun Java either. I get the following errors:

java.lang.ArrayIndexOutOfBoundsException: 0
        at LispList.nth(LispValue.java:239)
        at MikojoCustomizer.populateConjunctsForQuery(MikojoCustomizer.java:166)
        at MikojoCustomizer.commonSearchPanelInit(MikojoCustomizer.java:609)
        at MikojoCustomizer.<init>(MikojoCustomizer.java:1047)
        at MikojoApplet.init(MikojoApplet.java:72)
        at sun.applet.AppletPanel.run(AppletPanel.java:436)
        at java.lang.Thread.run(Thread.java:636)

java.lang.NullPointerException
        at MikojoCustomizer.setUpSearchOnlyCommands(MikojoCustomizer.java:554)
        at MikojoCustomizer.commonSearchPanelInit(MikojoCustomizer.java:616)
        at MikojoCustomizer.<init>(MikojoCustomizer.java:1047)
        at MikojoApplet.init(MikojoApplet.java:72)
        at sun.applet.AppletPanel.run(AppletPanel.java:436)
        at java.lang.Thread.run(Thread.java:636)

This looks like the exceptions are being thrown from the init of the applet's code. 

icedtea6: http://icedtea.classpath.org/hg/icedtea6

Closing this as NOTABUG.
If you believe otherwise feel free to reopen this bug.

--Andrew

The applet has changed, and I also get the index outofbounds, even in windows.
However this happens right away in windows whereas in linux I have to wait a long time with the processor running at 100% and before I get that error I see this:
 java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.1) (fedora-40.b18.fc12-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
java.lang.Exception: Applet initialization timeout
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:637)
	at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
	at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)
java.lang.RuntimeException: Failed to handle message: handle 67115799 for instance 1
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:660)
	at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
	at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)
Caused by: java.lang.Exception: Applet initialization timeout
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:637)
	... 2 more
host: collabrium.cs3-inc.com port: 5210
java.lang.ArrayIndexOutOfBoundsException: 0

Is this due to a difference between your version and mine?
If so, when will the changes reach me?  Is there a way I can try the newer version?

Hello Donald,

The stack trace you're getting right now is because the applet is doing a lot of stuff in its init code which takes really long, this causes the wait for setting the handle to time out. Thus your exception. This way of handling the message has been changed recently in the HEAD version and no longer does that.

After testing this with the HEAD version (or so called "bleeding-edge" in the following links) I only receive the two exception above, which are from the applet's init code.

You can follow the instructions at http://icedtea.classpath.org/wiki/Main_Page to build the latest version.

After you finished building the latest version, you will need to setup your browser to use the newly built plugin. 

--Andrew

(In reply to comment #3)
> The stack trace you're getting right now is because the applet is doing a lot
> of stuff in its init code which takes really long, this causes the wait for
> setting the handle to time out. Thus your exception. This way of handling the
> message has been changed recently in the HEAD version and no longer does that.
It's this "lot of stuff" that I find problematic since in windows this does not seem to happen - at least I don't notice the delay.  So the real question is what is going on in that long delay.
Is there a long delay in your head version?

Hi Donald,

Can you please try running it again with the following steps?

1. Close all firefox instances
2. Open a terminal and start firefox as :
   ICEDTEAPLUGIN_DEBUG=true firefox 2>&1 | tee console.log
3. Try to run the applet


Wait till it times out, and then attach the resulting console.log and ~/.icedteaplugin/java.stderr files

Created attachment 452003 [details]
.icedteaplugin/java.stderr

Created attachment 452007 [details]
console log

I don't see the expected errors after timeout, I waited a while and the processor was not busy so I killed it.  Anyhow, I hope that's helpful.

I think the "problem" in the last attempt is that the error causing the out of bounds was fixed in the mean while.

just want to report that after yum update getting
java-1.6.0-openjdk-src-1.6.0.0-41.1.8.2.fc12.x86_64
which fixes a lot of other stuff, the url above goes into 100% cpu mode for a minute and then gives me this
 java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.2) (fedora-41.1.8.2.fc12-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
java.lang.Exception: Applet initialization timeout
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:637)
	at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
	at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)
java.lang.RuntimeException: Failed to handle message: handle 62919065 for instance 1
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:660)
	at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
	at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)
Caused by: java.lang.Exception: Applet initialization timeout
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:637)
	... 2 more

However, when I then retry the same url it seems to work.

Hi Donald.

The IcedTea (Upstream project that yields the java-1.6.0-openjdk RPM) has no problems with http://collabrium.cs3-inc.com:8200/mikojo-test. I imagine you are seeing this issue due to Fedora being slightly out of date with upstream in terms of plugin updates.

We are working on mitigating it by splitting off the plugin/webstart package to deliver updates sooner. The next update in Fedora will be IcedTea 1.9.X, and it should have the fix.

(In reply to comment #11)
I guess that means that when I get a version of java that claims to be icedtea 1.9 then I should expect this problem to be solved.  Let me know if you have any idea when to expect that.

1.9 packages (1.9.1) are available in Fedora 14. Unfortunately those do not have the changes yet either. The changes will be in the 1.9.2 release that goes in Fedora.

We are hoping to release a new version in Fedora in ~ 1 month. If you are developer and are comfortable with compiling code, I'd be happy to send you instructions on how to try out the latest plugin from upstream. Now that it has been split, it is fairly easy to compile.

If you have Mercurial installed on Fedora, you can do:

hg clone http://icedtea.classpath.org/hg/icedtea-web

and then follow the instructions in README on how to compile.

Deepak, IcedTea-Web could go in without the 1.9.2 release.  You'd just need to disable building the plugin in the existing packages and delete javaws.

(In reply to comment #14)
> If you have Mercurial installed on Fedora, you can do:
> 
> hg clone http://icedtea.classpath.org/hg/icedtea-web
> 
> and then follow the instructions in README on how to compile.
> 
> Deepak, IcedTea-Web could go in without the 1.9.2 release.  You'd just need to
> disable building the plugin in the existing packages and delete javaws.

Ah, good point! It may take a while to test if upgradability works correctly (since there were be alternatives related changes related to plugin and javaws). I'll take a look at it tomorrow.

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

just upgraded to fc 14
java-1.6.0-openjdk-plugin-1.6.0.0-41.1.8.2.fc12.x86_64
I still see
$ java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.1) (fedora-44.1.9.1.fc14-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b06, mixed mode)
java.lang.NullPointerException
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:649)
	at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
	at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)
java.lang.RuntimeException: Failed to handle message: width 940 height 520 for instance 1
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:660)
	at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
	at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)
Caused by: java.lang.NullPointerException
	at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:649)
	... 2 more

but the applet seems to work, even without a long delay

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

FYI.. The warning is fixed in icedtea-web -- a new package that will be introduced in Fedora shortly.