Bug 1174152

Summary:	(6.4.0) listDeliveringMessages and listScheduledMessages in HQ but not accessible
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Shaun Appleton <sappleto>
Component:	HornetQ	Assignee:	Clebert Suconic <csuconic>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Miroslav Novak <mnovak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.2	CC:	bbaranow, cdewolf, jmesnil, kkhan, msvehla, myarboro
Target Milestone:	ER2
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
URL:	https://access.redhat.com/support/cases/00524250
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1174630 (view as bug list)		Environment:
Last Closed:	2019-08-19 12:38:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1174630, 1184141

Description Shaun Appleton 2014-12-15 09:45:58 UTC

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.

Comment 4 Ondřej Kalman 2015-01-14 10:54:31 UTC

Verified with 6.4.0.ER1

Comment 5 Ondřej Kalman 2015-01-19 14:25:38 UTC

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.

Comment 7 Clebert Suconic 2015-01-20 14:59:53 UTC

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.

Comment 8 Jeff Mesnil 2015-01-20 15:01:59 UTC

The fix is just to make the listDeliveringMessages available through the JMSQueueControl interface

Comment 11 Clebert Suconic 2015-01-20 21:46:32 UTC

listScheduledMessages is the same thing... so I will use this opportunity to also add the missing delegate.

Comment 12 Kabir Khan 2015-01-23 14:42:37 UTC

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.

Comment 13 Kabir Khan 2015-01-23 22:20:16 UTC

https://github.com/jbossas/jboss-eap/pull/2260 has been merged

Comment 15 Ondřej Kalman 2015-02-09 12:01:13 UTC

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?

Comment 16 Jeff Mesnil 2015-02-11 11:56:28 UTC

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)

Comment 17 Ondřej Kalman 2015-02-11 12:18:55 UTC

VERIFIED with 6.4.0.ER2