I have to disagree with some of the gurus here. In most cases a stateless or singleton bean is going to use an entityManager/hibernate session to get data to/from the DB. EM is not thread safe, using a singleton with read lock will cause concurrency issues on EM. So stateless in that case is the way to go as it'll have its own EM instance. For scalable applications this would work well.
Having strict pooling = false with proper max/min values (based on expected app load) will work as suggested. -- View this message in context: http://openejb.979440.n4.nabble.com/ConcurrentAccessTimeoutException-tp4661288p4661466.html Sent from the OpenEJB User mailing list archive at Nabble.com.
