[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jboss-user
Subject:    [jboss-user] [EJB/JBoss] - Re: MDB calling a session bean,
From:       rlperry <do-not-reply () jboss ! com>
Date:       2009-05-29 19:15:10
Message-ID: 13785948.1243624510914.JavaMail.jboss () tmp3 ! prod ! atl2 ! jboss ! com
[Download RAW message or body]

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, but when the server goes idle the \
JCA threads are deallocated, but the associated Stateless Beans are not.  So when the \
server gets busy again all new instances of my beans are created.

I am now working around this by setting MinimumPoolSize =MaximumPoolSize in \
jbossjca-service.xml.  For my application I really sorta like this configuration \
anyway.  

So for me the only question is how do we get deallocations when threads go away? 

View the original post : \
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234204#4234204

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234204
 _______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic