I would like to also note, that when attempting to monitor queue statistics appears to be deceiving. When using a command such as:
imqcmd metrics dst -b localhost:6076 -m con -t q -u admin -n jms_conduit_a_OutboundQueue
To monitor the consumer statistics of a jms dest, active/peak/avg consumers is ALWAYS 1.
But, it appears that app server is actually creating multiple instances of MDBs.
Is the "consumer" that the imqcmd shows related to the number of MDBs being used, or does it quite literally mean that Glassfish has a single TCP connection that it is consuming messages with, and then the app server is doing its own bean management as far as MDB bean pool sizes etc?
If so, is there a way to really monitor how many MDBs Glassfish is using to consume messages?
[Message sent by forum member 'asherwin' (asherwin)]
http://forums.java.net/jive/thread.jspa?messageID=273797