I'm using TomEE 7.0.4, EJB version 3.1
I often see this when making a high volume of calls to methods in
@Stateless classes:

javax.ejb.ConcurrentAccessTimeoutException: No instances available in
Stateless Session Bean pool.  Waited 30 SECONDS

I've set maxSize to 1000 in my tomee.xml and I still receive the error just
as soon as I would without maxSize specified at all, which leads me to
believe it's not doing anything. I see recommendations on this list to use
@Singleton with a read lockmode, but that doesn't seem to make a lot of
sense with our current arrangement.



Thanks!
-Kean

Reply via email to