Description of problem: listDeliveringMessages was introduced into HornetQ 2.3.0 via https://issues.jboss.org/browse/HORNETQ-763 but cannot be accessed via management methods. It appears in http://jbosslxr.gsslab.fab.redhat.com/lxr/as7/source/_projectlinks/hornetq/hornetq-server/src/main/java/org/hornetq/core/management/impl/QueueControlImpl.java but not in http://jbosslxr.gsslab.fab.redhat.com/lxr/as7/source/_projectlinks/hornetq/hornetq-jms-server/src/main/java/org/hornetq/jms/management/impl/JMSQueueControlImpl.java so is not usable. So this is a request to expose the functionality.
Verified with 6.4.0.ER1
Reopened. While testing 6.3.3 we discovered that this operation should be visible in JMS module not only in Core. I was confused previously by description in customer ticket which is not very clear. So i verified it because i fount this method in JMX.
Why is that an issue... you can look at the operation through the Core Queue on the QueueControl and you would be able to see it through JMX. JMX is not even enabled by default.
The fix is just to make the listDeliveringMessages available through the JMSQueueControl interface
listScheduledMessages is the same thing... so I will use this opportunity to also add the missing delegate.
Upgrade BZ1184141 (which has been merged) contains the HornetQ part of this work. https://github.com/jbossas/jboss-eap/pull/2260 which is not merged yet contains the management layer changes.
https://github.com/jbossas/jboss-eap/pull/2260 has been merged
Just to be clear. Delivering messages are all "uncommitted" messages in both directions (sent to the queue / consumed from the queue) , or only uncommitted messages which were consumed?
Delivering messages are messages sent by the server to the client that have not been consumed yet (i.e. they are on the wire on in the client's messages buffer)
VERIFIED with 6.4.0.ER2