stopping listener does not remove consumers

[gordon chung]

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.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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/

[OpenStack Infra (hudson-openstack)]

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