I have this problem with ActiveMQ and had been having pretty good luck with
StrictMaxPool, but in doing some testing with ThreadLocalPool, I learned that
my problem resolves back to the JCA thread pool. Basically as long as I am
keeping the server completely busy I do not leak Session Beans, bu
I am coming across this problem in EJB 2. Any idea how to fix this issue with
EJB 2 on Jboss 4.2.2 GA?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228458#4228458
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228458
I wanted to post some follow-up information, in case anyone had any additional
thoughts. This appears to be a bug in multiple versions of JBoss AS, including
apparently 5.0, where any time a stateless session bean is injected into an MDB
a new instance of that stateless session bean is created,
I have a nice little reproducible test case to see this behavior but I don't
know how to attach it to this posting.
Thanks,
Shreyas
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210891#4210891
Reply to the post :
http://www.jboss.org/index.html?module=bb&
This is the EXACT behavior we have been observing as well, in JBossAS 4.2.2,
which we have been trying to figure out how to work-around.
We have observed that any stateless session bean called from an MDB is never
released or any SLSB called from those SLSB's down the line.
View the original po
