stopping listener does not remove consumers

Bug #1397459 reported by gordon chung
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Low
Mehdi Abaakouk

Bug Description

with the eventlet executor, after calling stop() for notification listeners, the consumers still exist.

ie. run listener.stop() and then run sudo rabbitmqctl list_consumers. the consumers associated with listener still exist and is only killed if the entire service running the listener stops.

Mehdi Abaakouk (sileht)
Changed in oslo.messaging:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (master)

Fix proposed to branch: master
Review: https://review.openstack.org/138193

Changed in oslo.messaging:
assignee: nobody → gordon chung (chungg)
status: Confirmed → In Progress
Changed in oslo.messaging:
assignee: gordon chung (chungg) → Mehdi Abaakouk (sileht)
Mehdi Abaakouk (sileht)
Changed in oslo.messaging:
milestone: none → next-kilo
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on oslo.messaging (master)

Change abandoned by gordon chung (<email address hidden>) on branch: master
Review: https://review.openstack.org/138193
Reason: abandoning -- the correct usage is to use stop() and then wait() to close connection.

doc change: https://review.openstack.org/#/c/138788/

gordon chung (chungg)
Changed in oslo.messaging:
importance: Undecided → Low
Mehdi Abaakouk (sileht)
Changed in oslo.messaging:
milestone: 1.5.1 → next-kilo
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.messaging (master)

Reviewed: https://review.openstack.org/138788
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=254405d1055df2797723ef175cd56cfe6eb6392f
Submitter: Jenkins
Branch: master

commit 254405d1055df2797723ef175cd56cfe6eb6392f
Author: Mehdi Abaakouk <email address hidden>
Date: Wed Dec 3 18:01:46 2014 +0100

    Doc: 'wait' releases driver connection, not 'stop'

    This change documents that MessageHandlingServer.wait
    the released driver resources associated to this
    MessageHandlingServer instance.

    Like closing network connections to the broker.

    Closes bug: #1397459

    Change-Id: I3b0710faeb32ca8e9ee09b14aa1f79290c6061f5

Changed in oslo.messaging:
status: In Progress → Fix Committed
Changed in oslo.messaging:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers