Loading...

XML

Word

Printable

Affects:

Release Notes
GSS Priority:
Release Note Text:

Hide
In previous releases, the JMX operation `listDeliveringMessages()` did not return messages that were consumed by an AMQP JMS client in a transaction. The transactional messages are now returned correctly when the JMX operation `listDeliveringMessages()` is called.

Show
In previous releases, the JMX operation `listDeliveringMessages()` did not return messages that were consumed by an AMQP JMS client in a transaction. The transactional messages are now returned correctly when the JMX operation `listDeliveringMessages()` is called.
Release Note Status:
Documented as Resolved Issue
Target Release:

AMQ 7.2.3.GA
Upstream Jira:
https://issues.apache.org/jira/browse/ARTEMIS-1850
Steps to Reproduce:
Hide

send 20 messages to an Address

using AMQP jars to 0.26.0.redhat-1 (client 1.2) create a TRANSACTED consumer that consumes 20 messages from the address BUT do NOT call transaction commit().

inspect the queue's JMX attribute "Delivering Count" is 20.

invoke queue's JMX operation listDeliveringMessages() - it will return an empty list.
Show
send 20 messages to an Address using AMQP jars to 0.26.0.redhat-1 (client 1.2) create a TRANSACTED consumer that consumes 20 messages from the address BUT do NOT call transaction commit(). inspect the queue's JMX attribute "Delivering Count" is 20. invoke queue's JMX operation listDeliveringMessages() - it will return an empty list.

queues JMX attribute "Delivering Count" > 0 but the JMX operation "listDeliveringMessages()” is returning an empty list.

Intuitively I would expect the listDeliveringMessages() operation to list number of messages reported in the Delivering Count.