The follow up is appreciated - we hadn't touched upon any of the asynchronous parts of Kalyan's questions, so any pointers you're able to give are appreciated. The hanging threads appear to be fixed in 8.0.0.
Jon On Mon, Oct 14, 2019 at 10:46 AM Richard Monson-Haefel < monsonhae...@gmail.com> wrote: > Please ignore my previous email. I didn't see that Jon had already helped > with this. Good luck! > > On Mon, Oct 14, 2019 at 4:45 AM Richard Monson-Haefel < > monsonhae...@gmail.com> wrote: > > > Hi Kalyan, > > > > Are you using the @Asnycrhous annotation? If so, that's probably why you > > are seeing messages for the AsynchronousPool. I found this article which > > helps explain asynchronous EJBs > > > > https://www.tomitribe.com/blog/asynchronous-ejbs-on-tomee/ > > > > It mentions the max pool size is set, as a default of 5. As does this > > article: > > > > > https://tomee.apache.org/latest/docs/admin/configuration/application.html > > > > Have you tried to set that max pool size property to a higher number? If > > you can determine from logs the average number of invocations per second > at > > peak periods you could use that as a guide for setting the async pool > > size. If that's not possible try a couple different max pool sizes (e.g. > > 20, 50, 100) and see if that helps. I don't think - although I'm not sure > > about this - that setting the max pool size higher is going to effect > > performance much but I'm not sure about that. > > > > Richard > > > > On Thu, Oct 3, 2019 at 3:16 PM Kalyan <kalyanfrem...@gmail.com> wrote: > > > >> Hello, > >> I am getting following error in my application. > >> > >> avax.ejb.ConcurrentAccessTimeoutException: No instances available in > >> Stateless Session Bean pool. Waited 30 SECONDS > >> at > >> > >> > org.apache.openejb.core.stateless.StatelessInstanceManager.getInstance(StatelessInstanceManager.java:226) > >> at > >> > >> > org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:204) > >> at > >> > >> > org.apache.openejb.core.ivm.EjbObjectProxyHandler.synchronizedBusinessMethod(EjbObjectProxyHandler.java:265) > >> at > >> > >> > org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:260) > >> at > >> > >> > org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:89) > >> at > >> > >> > org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:349) > >> > >> > >> > >> My application is heavily used. Looks like not enough instances of > beans. > >> > >> I saw this post to increase the pool size > >> > >> https://tomee.apache.org/admin/configuration/containers.html > >> > >> > >> and changed my configuration as > >> > >> > java.naming.factory.initial=org.apache.openejb.core.LocalInitialContextFactory > >> openejb.deployments.classpath.ear=false > >> > >> myApp = new://Container?type=STATELESS > >> myApp.AccessTimeout = 30 seconds > >> *myApp.MaxSize = 40* > >> myApp.MinSize = 0 > >> myApp.StrictPooling = true > >> myApp.MaxAge = 0 hours > >> myApp.ReplaceAged = true > >> myApp.ReplaceFlushed = false > >> myApp.MaxAgeOffset = -1 > >> myApp.IdleTimeout = 0 minutes > >> myApp.GarbageCollection = false > >> myApp.SweepInterval = 5 minutes > >> myApp.CallbackThreads = 5 > >> myApp.CloseTimeout = 5 minutes > >> myApp.UseOneSchedulerThreadByBean = false > >> myApp.EvictionThreads = 1 > >> > >> > >> On the server start up I see > >> > >> INFO - Configuring Service(id=myApp, type=Container, provider-id=Default > >> Stateless Container) > >> > >> DEBUG - Containers : 1 > >> DEBUG - Type Container ID > >> DEBUG - STATELESS myApp > >> DEBUG - Deployments : 5 > >> DEBUG - Type Deployment ID > >> > >> /Question i have is / > >> How would i know if the bean size is increased ? I don't see any log > >> message for it. > >> > >> /Secondly I also see / > >> > >> DEBUG - Using default 'openejb.tempclassloader.skip=none' Possible > values > >> are: none, annotations, enums, all or NONE or ALL > >> DEBUG - Using default 'AsynchronousPool.Size=5' > >> DEBUG - Using default 'AsynchronousPool.CorePoolSize=5' > >> DEBUG - Using default 'AsynchronousPool.MaximumPoolSize=5' > >> DEBUG - Using default 'AsynchronousPool.QueueSize=5' > >> DEBUG - Using default 'AsynchronousPool.KeepAliveTime=60 SECONDS' > >> DEBUG - Using default 'AsynchronousPool.AllowCoreThreadTimeOut=true' > >> DEBUG - Using default 'AsynchronousPool.QueueType=linked'. Possible > >> values > >> are: array, linked, priority, synchronous > >> DEBUG - Using default 'AsynchronousPool.OfferTimeout=30 SECONDS' > >> DEBUG - Using default 'AsynchronousPool.ShutdownWaitDuration=1 MINUTES' > >> > >> > >> What's the AsynchronousPool ??? > >> > >> > >> Please help me to sort this issue? > >> I'm running into this issues in production. > >> > >> > >> > >> thanks > >> Kalyan > >> > >> > >> > >> > >> > >> > >> > >> -- > >> Sent from: > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html > >> > > > > > > -- > > Richard Monson-Haefel > > https://twitter.com/rmonson > > https://www.linkedin.com/in/monsonhaefel/ > > > > > -- > Richard Monson-Haefel > https://twitter.com/rmonson > https://www.linkedin.com/in/monsonhaefel/ >
