No and Yes.
Thanks for the response Adrian.
One quick follow up - is it possible to view the setting using JMX? I tried to find it in the web console but couldn't - any help?
Seems to me you can change the max size at runtime, having just looked at the code. If the max size was reduced to, say 10 and there were 50 messages already added, the depth would not be reduced, but no new messages could be added.
Look for the attribute MaxDepth, for MBeans belonging to the "jboss.mq.destination" domain.
Er, I was thinking of MaxDepth of the message queue, not the number of pooled MDBs. (I'm sleepy...)
Very few of the ejb configurations are managable at
In this case the number of concurrent sessions is passed
to the ConnectionConsumer when it is constructed.
You would have to stop the container invoker and reconnect
to JMS (even if the option were exposed which it is not)