OpenStack library for messaging
b888ee3ebf
The Notification Listener Tracker class is not threadsafe, so when a test stop an already stopped listener this one can be restarted, due to concurrency access of the threads list and concurrency execution of the start/stop/wait method of the notification listener. This result of a lockup of the test or a listener can continue to got unepxected message. This change fixes that by never stop the tread with the tracker callback but only manually with the test. This test also rename some 'Listener' to 'Server', to not mismatch the driver listener from the notification listener. Closes-bug: #1410902 Change-Id: I4777c7dd0ba71c61850d36641e85f33f9461e9c1 |
||
---|---|---|
doc/source | ||
etc | ||
oslo | ||
oslo_messaging | ||
oslo.messaging/locale | ||
tests | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
amqp1-requirements.txt | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements-py3.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements-py3.txt | ||
test-requirements.txt | ||
tox.ini |
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
See also: Library Documentation