Your configuration is for the session pool.
You are looking at the ejb pool.
The session pool configuration will be exposed on the container invoker
from 3.2.4RC1. To make changes take affect, you must restart delivery.
Thanks for the message. Couple follow on questions and want to make sure I understood the whole thing correctly:
If I want to know how many concurrent messages that MDB can handle, which pool should I look, session pool or EJB pool?
It is kind easy to guess what is EJB pool. What is exactly the definition of session pool? what is
the definition of the session here?
I am guess that it doesnot make sense to have
more instance in EJB pool than instances in session pool. Is that right?
1) The session pool. You showed it before. They are ServerSessions that wrap
2) The EJB pool is largely irrevelent unless your MDBs are expensive to construct.