qpid driver in topology 2 can cause build up of response messages
Bug #1318742 reported by
Gordon Sim
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo-incubator |
Fix Released
|
High
|
Gordon Sim | ||
oslo.messaging |
Fix Released
|
High
|
Gordon Sim |
Bug Description
If topology 2 is selected for the qpid driver and the connection is lost then re-established (and the broker state is not lost as part of this), a new receiver is created for responses and as the link name is not specified, a new queue will be created, though the same routing key is used. The old response queue is left there (as auto-delete is off by default), but because the same routing key is being used, all responses for any subsequent requests issued will be enqueued on both old and new queue. Nothing is subscribed to the old queue so the messages there will simply build up.
Changed in oslo.messaging: | |
importance: | Undecided → High |
Changed in oslo: | |
importance: | Undecided → High |
tags: | added: icehouse-backport-potential |
Changed in oslo: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in oslo.messaging: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
A workaround is to set the amqp_auto_delete option to True when using that topology and the qpid driver.