openstack/oslo.messaging
Code Issues Proposed changes

Consider the topic parameter as an array in client-notify

Browse Source 
Without this fix, the simulator splits the "topic" value in different
strings, in notify-client case
Instead of having one queue there are multi-queues.
See [1] for more details

Closes-Bug: #1824339

1- https://bugs.launchpad.net/oslo.messaging/+bug/1824339

Change-Id: I438c7279d584bdb00da18477a83d5e2a53c588c4
This commit is contained in:
Gabriele 2019-04-11 13:48:40 +02:00
parent e99af8ca57
commit 0ad4a204b3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tools/simulator.py
View File

@ -549,7 +549,7 @@ def spawn_notify_clients(threads, topic, transport, message_count,
wait_after_msg, timeout, duration):
p = eventlet.GreenPool(size=threads)
for i in six.moves.range(threads):
client_builder = functools.partial(NotifyClient, i, transport, topic,
client_builder = functools.partial(NotifyClient, i, transport, [topic],
wait_after_msg)
p.spawn_n(send_messages, i, client_builder, message_count, duration)
p.waitall()