Uploaded image for project: 'Queued Asynchronous Activation over RabbitMQ'
  1. Queued Asynchronous Activation over RabbitMQ
  2. QAARQ-29

RabbitMQ monitoring does not acknowledge status messages

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 1.8
    • 1.7.1
    • monitoring
    • None

      The RabbitMQ activation consumer, ConfirmationConsumer (info.magnolia.rabbitmq.consumers.ConfirmationConsumer) does not acknowledge status messages in the ACK queue. 

      ACK messages in the ACK queue are processed, but the ACK messages stay in the ACK in an unacked state. Disconnecting the ack consumer from the queue will reset all messages in the ACK queue to a ready state but reconnecting the ack consumer will re-process the messages.

      info.magnolia.rabbitmq.consumers.ConfirmationConsumer#processMessage should have a call to the ACK client basicAck to acknowledge the message.

        Acceptance criteria

              awarinner Andrew Warinner
              awarinner Andrew Warinner
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD