Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-919

Expiry statistics are not being updated

XMLWordPrintable

    • Compatibility/Configuration, User Experience
    • Hide

      1) Create queue 

      java  -jar /var/dtests/node_data/clients/amqx.jar  queue --host <ip>:1099 --action add --name 'test_dead_letter_queue_with_expired_messages'

      2) Send message with ttl time (1 sec)

       
java  -jar /var/dtests/node_data/clients/aac1.jar sender  --log-msgs dict --broker <ip>:5672 --conn-username admin --conn-password admin --address "test_dead_letter_queue_with_expired_messages" --count 3 --msg-content "ABC" --msg-durable yes --msg-ttl 1000 --msg-priority 8

      3) Either wait and receive it from ExpiryQueue (when reaper kicks in ~30secs max) or read them from original queue (nothing should be received) and then read from ExpiryQueue

      java  -jar /var/dtests/node_data/clients/aac1.jar receiver  --log-msgs dict --broker <ip>:5672 --conn-username admin --conn-password admin --address ExpiryQueue --count 0

      4) Observe expiry stats - they are not being updated.

      Show
      1) Create queue java -jar /var/dtests/node_data/clients/amqx.jar queue --host <ip>:1099 --action add --name 'test_dead_letter_queue_with_expired_messages' 2) Send message with ttl time (1 sec) java -jar /var/dtests/node_data/clients/aac1.jar sender --log-msgs dict --broker <ip>:5672 --conn-username admin --conn-password admin --address "test_dead_letter_queue_with_expired_messages" --count 3 --msg-content "ABC" --msg-durable yes --msg-ttl 1000 --msg-priority 8 3) Either wait and receive it from ExpiryQueue (when reaper kicks in ~30secs max) or read them from original queue (nothing should be received) and then read from ExpiryQueue java -jar /var/dtests/node_data/clients/aac1.jar receiver --log-msgs dict --broker <ip>:5672 --conn-username admin --conn-password admin --address ExpiryQueue --count 0 4) Observe expiry stats - they are not being updated.

      Message expiry statistics do not work at all with the latest 7.1.0 CR1 build.

      7.0.3 GA Expiry stats -> works as expected, counters are being updated accordingly.
      7.1.0 CR1 -> messages are expired, but expiry counter is not updated accordingly (stays on 0).

      Messages in attached picture were sent in bulk of 3. All were successfully expired, but no statistics updated.

        1. expiry_number_fail.png
          expiry_number_fail.png
          212 kB

              sknot@redhat.com Stanislav Knot (Inactive)
              mtoth@redhat.com Michal Toth
              Michal Toth Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: