Hmm
Tried with three threads. Even with those settings in sub-ejb-jar.xml, glassfish creates 3 EJBs to handle the load---one for each thread running in y test program. Yikes. Apparently, once the EJBs are executing on behalf of some client, glassfish considers them out-of-the-pool and creates new instances as necessary. And it seems there is no real possibility to set a cap on the number of simultaneously executing instances of an EJB.
With my settings, once the client threads terminates, the pool shortly shows 3 EJBS in the pool. Two of them quickly get deleted, because the max-pool-size. The last gets deleted after 30 seconds. So everything works as expected except the fact that executing beans are not counted against the max-pool-size value.
Big problem.
Now - how to file a bug report?
[Message sent by forum member 'jablo' ]
http://forums.java.net/jive/thread.jspa?messageID=373945