Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Release Note Text:
Undefined
Steps to Reproduce:
Hide

Start the broker with configuraiton: <address name="newtopic">
<multicast>
<queue name="newtopic" />
</multicast>
</address>

Run a subscriber, subscribing to above multicast address with session.DUPS_OK_ACKNOWLEDGE.

Run a publisher

Check the output stats : ./artemis queue stat

Wait and see if the MESSAGES_ACKED count gets updated lazily ?

MESSAGE_COUNT and MESSAGES_ADDED gets updated correctly.
Show
Start the broker with configuraiton: <address name="newtopic"> <multicast> <queue name="newtopic" /> </multicast> </address> Run a subscriber, subscribing to above multicast address with session.DUPS_OK_ACKNOWLEDGE. Run a publisher Check the output stats : ./artemis queue stat Wait and see if the MESSAGES_ACKED count gets updated lazily ? MESSAGE_COUNT and MESSAGES_ADDED gets updated correctly.
Market:

If there is a durable subscriber , subscribed with DUPS_OK_ACKNOWLEDGE mode.

When is it the messages are acknowledged ? When does the MSSAGES_ACKED count get updated ?
This acknowledgment mode instructs the session to lazily acknowledge the delivery of messages, what are the actual semantics of DUPS_OK
Not clear if the messages are acknowledged in batch OR after certain interval of time !
Tried to test this with a durable subscriber (a.xyz) clientID, published 2 messages. The stats are as below:

./artemis queue stat :

Here the MESSAGE_COUNT and MESSAGE_ADDED is getting updated, while the messages are being consumed by the java test client (in local setup) , but the MESSAGES_ACKED is still the same.

Do you have any clue, when does the MESSAGES_ACKED gets updated ?
Is it a bug ?

Note: With AUTO_ACKNOWLEDGE we can see an immediate updated MESSAGES_ACKED count in stats but not in DUPS_OK !

*Also, tested with AMQ 7.7 which still shows no updates to the MESSAGES_ACKED count