Reject messages that can't be acknowledged
Bug #1364543 reported by
Joshua Harlow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Fix Released
|
Medium
|
Joshua Harlow | ||
| 0.5 |
New
|
Undecided
|
Unassigned | ||
Bug Description
When a message can't be acked we should attempt to reject it (not requeue it since that will just mean we get the message back again) instead of just dropping it on the floor (which is bad).
| Changed in taskflow: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Joshua Harlow (harlowja) |
| Changed in taskflow: | |
| status: | New → In Progress |
| Changed in taskflow: | |
| milestone: | none → next-juno |
| Changed in taskflow: | |
| milestone: | next-juno → next-kilo |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to taskflow (master) | #1 |
| Changed in taskflow: | |
| status: | In Progress → Fix Committed |
| Changed in taskflow: | |
| status: | Fix Committed → Fix Released |
| Changed in taskflow: | |
| milestone: | next-kilo → none |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit e389ee61d109a6b
Author: Joshua Harlow <email address hidden>
Date: Sun Aug 17 00:22:12 2014 -0700
Reject WBE messages if they can't be put in an ack state
Attempt to reject messages that could not be acknowledged
so that those messages could be resent (requeueing is not
appropriate since it will just cause the message to come
back).
Fixes bug 1364543
Change-Id: I2cb33b39be9505