IBM support has responded with the following -
/Here, level 2's understanding is correct i.e "maxPoolDepth" is the
maximum number of server sessions in the server session pool used by the
connection consumer, which controls the number of MDB instances i.e the
Maximum number of MDB instances that can be instantiated is equal to the
value configured in "maxPoolDepth" property.
It is the responsibility of the EJB Container to either create a new
instance of the message-driven bean, or get an instance of the
message-driven bean from an internal pool not the WebSphere MQ Resource
Adapter.
/
So, my question is - is the maxPoolDepth property being ignored by tomEE. As
I said in my I am seeing this behavior when I use websphere mq resource
adapter.
--
View this message in context:
http://openejb.979440.n4.nabble.com/MDB-being-instantiated-on-every-message-tp4665830p4666167.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
