This has more to do with the specific Stateless Session Bean pooling behavior in a given
ejb container implementation. In Glassfish, the max-pool-size for stateless session beans
is not blocking. It just governs the total number of instances that are kept in memory. The
container will create as many bean instances as are needed to process the number of
concurrent requests on the same bean. You would certainly want to tune the pool settings
to best match your expected runtime load but there's nothing inherently blocking about using
stateless session beans. In the case of a facade bean there is typically not a huge amount
of instance state, so creating a large number of instances usually won't represent a real
resource burden in the application server JVM.
--ken
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=210076