[QAARQ-29] RabbitMQ monitoring does not acknowledge status messages Created: 14/Dec/18 Updated: 11/Jul/22 Resolved: 14/Dec/18 |
|
| Status: | Closed |
| Project: | Queued Asynchronous Activation over RabbitMQ |
| Component/s: | monitoring |
| Affects Version/s: | 1.7.1 |
| Fix Version/s: | 1.8 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Andrew Warinner | Assignee: | Andrew Warinner |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| 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. |