Please file a bug report.
On Mon, Dec 21, 2009 at 7:51 PM, <glassfish_at_javadesktop.org> wrote:
> I am seeing similar behavior when invoking a remote EJ B. The max pool size
> is completely ignored.
>
> The whole pooling mechanism was originally created to limit resources (i.e.
> limit concurrent access to services) and to reduce the overhead of
> construction. The current design of the ejb and mdb pools clearly fails at
> all of these. This behavior of pooling is really unexpected and also
> inefficient.
>
> Can this be solved any time soon?
> [Message sent by forum member 'erikengerd' (erik_at_brakkee.org)]
>
> http://forums.java.net/jive/thread.jspa?messageID=372208
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>