Too many oslo_messaging warnings using wait() after start()

[Lingxian Kong]

When start mistral service using CLI, we will see a lot of oslo_messaging warnings like the following:
......
2015-11-09 22:05:02.996 29405 WARNING oslo_messaging.server [-] wait() should be called after stop() as it waits for existing messages to finish processing
2015-11-09 22:05:02.997 29405 WARNING oslo_messaging.server [-] wait() should be called after stop() as it waits for existing messages to finish processing
2015-11-09 22:05:03.996 29405 WARNING oslo_messaging.server [-] wait() should have been called after stop() as wait() waits for existing messages to finish processing, it has been 1.00 seconds and stop() still has not been called
2015-11-09 22:05:03.997 29405 WARNING oslo_messaging.server [-] wait() should have been called after stop() as wait() waits for existing messages to finish processing, it has been 1.00 seconds and stop() still has not been called
......

According to http://docs.openstack.org/developer/oslo.messaging/notification_listener.html, the correct usage is to call stop() before wait(), so in mistral case, we should never call stop() and wait() in initialization of engine and executor service.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/243146
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=ec28a305d91139ef5d307fa56ad289a635e37a90
Submitter: Jenkins
Branch: master

commit ec28a305d91139ef5d307fa56ad289a635e37a90
Author: Lingxian Kong <email address hidden>
Date: Mon Nov 9 22:47:29 2015 +0800

    Removing wait() when initializing notification listener

    According to [1],the correct usage is to call stop() before wait(), so in
    mistral case, we should never call stop() and wait() in initialization of
    engine and executor service.

    [1]:
    http://docs.openstack.org/developer/oslo.messaging/notification_listener.html

    Change-Id: Ic6a802bff35a6a6fdfadf38474782efd12fd34d8
    Closes-Bug: #1514459

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/249593

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/249593
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=73d783eb90676a42a59495246d316421417ea2e1
Submitter: Jenkins
Branch: stable/liberty

commit 73d783eb90676a42a59495246d316421417ea2e1
Author: Lingxian Kong <email address hidden>
Date: Mon Nov 9 22:47:29 2015 +0800

    Removing wait() when initializing notification listener

    According to [1],the correct usage is to call stop() before wait(), so in
    mistral case, we should never call stop() and wait() in initialization of
    engine and executor service.

    [1]:
    http://docs.openstack.org/developer/oslo.messaging/notification_listener.html

    Change-Id: Ic6a802bff35a6a6fdfadf38474782efd12fd34d8
    Closes-Bug: #1514459
    (cherry picked from commit ec28a305d91139ef5d307fa56ad289a635e37a90)

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/mistral 2.0.0.0b1 development milestone.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/mistral 1.0.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/mistral 1.0.1 release.