"[EMAIL PROTECTED]" wrote : It is very
| difficult to achieve a controlled shutdown that doesn't leaving
hanging/orphaned
| threads lying around.
To be later removed when they pass the idle timeout ("long after" the thread
pool is dead).
View the original post :
http://www.jboss.com/index.h
"Thoennes" wrote :
| Dough Lea, the creator of the oswego-concurrent package, said the reason
was an unsupported way how JBoss used the thread pool settings, but Adrian
regarded it as a bug in the lib.
|
It is a bug. Just because Doug no longer supports it, doesn't stop it being a
bug. ;-
Thanks for your help. I tried the new concurrent.jar that came with jboss
3.2.8, but it didn't fix the problem. In fact, whiel the problem still
occured, the event handling seemed to be out of order.
I'll have to try switching completely to 3.2.8 when I have the chance. When I
get around to
In this JBoss version, oswego-concurrent thread pools are used to process the
messages. Every message picked up is handed over to the thread pool for
processing.
If the thread pool is set to 1 (using maximumSize), the MDB acts as a singleton.
If some reasons a thread from the thread pools exits
And this is a bug in oswego-concurrent anyway :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922850#3922850
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922850
---
Hmm, I would at least try to switch to 3.2.7. There's been many fixed bugs.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922746#3922746
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922746
--
I should mention that if this is a known bug that has been fixed, I may be able
to make a case to upgrade to a newer version of jboss.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922679#3922679
Reply to the post :
http://www.jboss.com/index.html?
