More wild assertions.
The bug you link to has already been fixed in JBoss4.
The error message says you are missing a class.
I have no idea why the JDK in your browser isn't you telling the class that is missing?
But if you look at the source code,
you will see it is NestedThrowable.Util which is in jboss-commons.jar
Right. This bug is fixed. While debugging, I found this exception:
org.jboss.mq.SpyJMSException: Cannot disable the connection with the JMS server; - nested throwable: (java.io.IOException: Client is not connected) at org.jboss.mq.Connection.doStop(Connection.java:1289) at org.jboss.mq.Connection.stop(Connection.java:718) at ch.steria.tbazh.applet.TestApplet.stop(TestApplet.java:57) at sun.applet.AppletPanel.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Client is not connected at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:226) at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:192) at org.jboss.mq.il.uil2.UILServerIL.setEnabled(UILServerIL.java:162) at org.jboss.mq.Connection.doStop(Connection.java:1285) ... 4 more
It only happens with more than one applet with the same code on a single webpage. I use now signed applets, the NoClassDefFoundError disapeared.
Before the reload, the applets are able to print JMS messages to stdout, so there are connections to JBossMQ.
I think there is a race condition in the connection code. The source of a demo applet, a html document and the necessary jars are available:
There is no JMS service running there. So the applet will not work.
Is this behavior reproducible and is it possible to fix it?