Bugs item #932326, was opened at 2004-04-09 14:38
Message generated for change (Settings changed) made by ejort
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=932326&group_id=22866
Category: JBossMQ
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Danielius Jurna (jurna)
Assigned to: Adrian Brock (ejort)
Summary: JBossMQ client crash when running from java applet
Initial Comment:
If you are running JBossMQ client from applet, after
closing/ reopening the applet, JBossMQ client crashes.
Stack trace from java console:
org.jboss.mq.SpyJMSException: Cannot start a the client
IL service; - nested throwable:
(java.lang.IllegalThreadStateException)
org.jboss.mq.SpyJMSException: Cannot start a the client
IL service; - nested throwable:
(java.lang.IllegalThreadStateException)
at
org.jboss.mq.Connection.startILService(Connection.java:962)
at org.jboss.mq.Connection.<init>(Connection.java:249)
at org.jboss.mq.Connection.<init>(Connection.java:315)
at
org.jboss.mq.SpyConnection.<init>(SpyConnection.java:60)
at
org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFactory.java:78)
at
.....
Caused by: java.lang.IllegalThreadStateException
at java.lang.ThreadGroup.add(ThreadGroup.java:798)
at java.lang.Thread.init(Thread.java:301)
at java.lang.Thread.<init>(Thread.java:438)
at
org.jboss.mq.il.http.HTTPClientILService.start(HTTPClientILService.java:120)
at
org.jboss.mq.Connection.startILService(Connection.java:954)
... 54 more
If you clear classloader cash (pressing 'x' in java
console) JBossMQ client works again.
----------------------------------------------------------------------
Comment By: Danielius Jurna (jurna)
Date: 2004-04-19 19:44
Message:
Logged In: YES
user_id=762374
The work around this bug is preatty simple. You just have to add these
lines before connecting to JbossMQ:
if(org.jboss.mq.Connection.threadGroup.isDestroyed()) {
org.jboss.mq.Connection.threadGroup = new ThreadGroup("JBossMQ
Client Threads");
}
So fix must also be pretty simple.
The problem I think is that when closing an applet, JVM kills all thread
groups in that applet, but JVM and classloaders are not killed.
Bug reproduced using Sun J2SDK 1.4.2, Mozilla (Win, Linux), IE6.
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2004-04-19 14:58
Message:
Logged In: YES
user_id=9459
This sounds like a JVM bug to me.
Please state which VM/browser you are using.
One simple fix would be to ignore the ThreadGroup processing
if it fails. It isn't important. Can you try that?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=932326&group_id=22866
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
