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

ActiveMQServer.updateQueue or cli.updateQueue is broken, may lose messages

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • AMQ 7.0.3.GA
    • AMQ 7.0.2.GA
    • None
    • None

    • Released 7.0.2 GA broker

    • Release Notes, User Experience
    • Hide
      Using the `artemis queue update` command to modify queue attributes results in messages being lost or removed when the broker is restarted.
      To workaround this issue, do not use this command to modify queues in a production system.
      Show
      Using the `artemis queue update` command to modify queue attributes results in messages being lost or removed when the broker is restarted. To workaround this issue, do not use this command to modify queues in a production system.
    • Documented as Resolved Issue
    • Workaround Exists
    • Hide

      Do not update Queues in a production system.

      Show
      Do not update Queues in a production system.
    • Hide

      1. create a durable queue

      java  -jar /var/dtests/node_data/clients/amqx.jar  queue  --action add --name update_me_queue --durable true

      2. Send few messages there

      java -jar /var/dtests/node_data/clients/aoc7.jar sender --conn-username admin --conn-password admin --count 10 -a update_me_queue --log-msgs dict

      3. perform any update on queue property

      jboss-amq-7-i0/bin/artemis  queue update --max-consumers 10 --name update_me_queue --user admin --password admin --anycast

      4. Restart broker and observe that queue is not present and messages are lost.

      Show
      1. create a durable queue java -jar /var/dtests/node_data/clients/amqx.jar queue --action add --name update_me_queue --durable true 2. Send few messages there java -jar /var/dtests/node_data/clients/aoc7.jar sender --conn-username admin --conn-password admin --count 10 -a update_me_queue --log-msgs dict 3. perform any update on queue property jboss-amq-7-i0/bin/artemis queue update --max-consumers 10 --name update_me_queue --user admin --password admin --anycast 4. Restart broker and observe that queue is not present and messages are lost.

      When one sends a message to a durable queue and updates this queue, the queue changes its ID and upon next restart all the messages are removed as queue with that id does not exist.

              csuconic@redhat.com Clebert Suconic
              mtoth@redhat.com Michal Toth
              Michal Toth Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: