Ah OK -- duh -- thanks again. : )
On Wed, Jan 8, 2014 at 10:05 AM, Romain Manni-Bucau <[email protected]>wrote: > see > http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2014/1/8 Stuart Easterling <[email protected]>: > > One other question, what does the > > > > AsynchronousPool.KeepAliveTime > > > > property do? > > > > I assume something happens to the pool if it has been idle for the time > > specified? is it reduced to CorePoolSize? or are the Threads disposed of? > > > > Can it be set to 0? > > > > Best, > > Stuart > > > > > > On Wed, Jan 8, 2014 at 9:51 AM, Stuart Easterling < > > [email protected]> wrote: > > > >> OK so the behavior is expected, and configurable, as described in the > link > >> Romain provided: > >> > >> https://issues.apache.org/jira/browse/TOMEE-382 > >> > >> I've used the properties > >> > >> AsynchronousPool.CorePoolSize > >> AsynchronousPool.MaximumPoolSize > >> > >> and the thread pool (and thus the number of async beans that can be > >> accessed) can increase above the default number of 3. > >> > >> So the developer can configure this behavior -- many thanks for the > >> clarification ! : ) > >> > >> Best, > >> Stuart > >> > >> > >> On Wed, Jan 8, 2014 at 3:10 AM, Romain Manni-Bucau < > [email protected]>wrote: > >> > >>> yep, like you have a single fridge in your kitchen (pool of stateless) > >>> and everybody uses it (thread pool(s)). > >>> > >>> As usually the smaller pool will limit others indirectly > >>> Romain Manni-Bucau > >>> Twitter: @rmannibucau > >>> Blog: http://rmannibucau.wordpress.com/ > >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau > >>> Github: https://github.com/rmannibucau > >>> > >>> > >>> > >>> 2014/1/8 Anthony Fryer <[email protected]>: > >>> > So there's a sync thread pool (ie. when called by a > HttpServletRequest) > >>> and > >>> > if that thread calls a stateless session EJB method synchronously, it > >>> uses > >>> > that same thread and is only limited by the stateless session pool > >>> size. If > >>> > an async call is made, then is uses the async thread pool (default > size > >>> 3) > >>> > and then if that thread calls an EJB method, it will take that EJB > >>> instance > >>> > from the same EJB pool as the sync thread? > >>> > > >>> > I think what i'm trying to ask is that the stateless session pool > size > >>> of > >>> > 100 will be used across both sync and async thread pools? The > problem > >>> here > >>> > is that the async thread pool size is only 3. Is that correct? > >>> > > >>> > Cheers, > >>> > > >>> > Anthony > >>> > > >>> > > >>> > > >>> > -- > >>> > View this message in context: > >>> > http://openejb.979440.n4.nabble.com/Re-stateless-bean-pool-all-beans-not-available-async-business-method-causes-problem-tp4667020p4667034.html > >>> > Sent from the OpenEJB User mailing list archive at Nabble.com. > >>> > >> > >> >
