Hello, So I've doubled maxSize to 40 and I'm still seeing the same problem of timeouts encountered while waiting for an available stateless bean, which was never an issue until tomee 8 was introduced.
Is there any known consideration with tomee 8 vs. 7 that the number of available instances in a stateless pool would wind up being somehow smaller, to the point that the pool runs out? On Sat, Oct 3, 2020 at 10:57 PM Kean Erickson <kean.erick...@gmail.com> wrote: > I am using a BeanManager to acquire classes annotated @Stateless in > multiple threads. This worked fine in 7.1.3, but now in 8.0.3 I'm receiving > this error: > > javax.ejb.ConcurrentAccessTimeoutException: No instances available in > Stateless Session Bean pool. Waited 30 SECONDS > > I see a number of these exceptions until the machine roughly runs out of > memory and restarts (though there's never an OutOfMemoryError in logs). I > had encountered this error in the past and solved it completely by > increasing the maxSize to 20 in tomee.xml: > > <Container id="StatelessContainer" type="STATELESS"> > maxSize = 20 > </Container> > > Is there any reason that I would need to boost this value in tomee 8 > compared to tomee 7? Or any reason the memory footprint would be different > enough to cause a crash. No other differences, same configuration > > Thanks, > -Kean > >
