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

2019-10-10 Thread Jonathan Gallimore
Setting MaxTotal, InitialSize, MinIdle, and MaxIdle enable you to control whether and when the pool will grow or shrink - http://commons.apache.org/proper/commons-dbcp/configuration.html. I'd avoid the urge to change more parameters if you can as it adds more variables. It looks like a code

Re: Problem with MessageConsumers under TomEE 8.0.0

2019-10-10 Thread Jonathan Gallimore
That's interesting. We'll see if we can create some test cases for these different scenarios. Jon On Thu, Oct 10, 2019 at 4:55 PM Ihsan Ecemis wrote: > > Sorry I just had time to make these experiments. > > Having the following (setting transacted = false) did not fix the problem > if we do

Re: Problem with MessageConsumers under TomEE 8.0.0

2019-10-10 Thread Ihsan Ecemis
Sorry I just had time to make these experiments. Having the following (setting transacted = false) did not fix the problem if we do not use try-with-resources: final Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); On the other hand, when we added