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

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: 1.7.1
    • Fix Version/s: 1.8
    • Component/s: monitoring
    • Labels:
      None

      Description

      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.

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Checklists

                    DoD