I dropped your settings into TomEE 8 here, and checked the pool for my EJB via JMX (openejb.management -> Pool -> openejb -> <empty> -> (file path) -> (bean) -> Attributes. It showed with a max size of 40. 1 instance pooled, but I'd expect that to grow to the max size.
I'd suggest getting a jstack and looking for threads with org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:204) in the trace, and see if you have something locked or running slowly. I'll happily look at a jstack if you wish, but it may have some information you don't want to post publicly (check the content of the jstack before posting). Jon On Thu, Oct 3, 2019 at 9:50 PM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Hi > > What version of TomEE are you using? > > Jon > > On Thu, Oct 3, 2019 at 9: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 >> >
