Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not work for dynamic work queues #27

Open
sdas191 opened this issue Sep 3, 2015 · 4 comments
Open

Does not work for dynamic work queues #27

sdas191 opened this issue Sep 3, 2015 · 4 comments

Comments

@sdas191
Copy link

sdas191 commented Sep 3, 2015

The AMQP consumer is reusing the same queue/exchange values for every subsequent sampler execution. This does not work for use-cases which have a dynamic work-queue to pull the mq-message from.

@jlavallee
Copy link
Owner

Pull requests welcome :)

@the-nicolas
Copy link

Has anyone found some fix for that - or is there some other fork?

Even the example RPC_Load_Test from the repo is not working with some normal "RPC-Echo server".

In every new iteration the message is send with the correct "reply_to" header set, but the consumer is not consuming from that new random queue. In Rabbit-Web you also see, that just one random-return queue is created and it never changes.

@the-nicolas
Copy link

Have a nice solution for RPC testing now #31

@arijitchanda
Copy link

Hi, has any one used it to connect to azure iot hub. please let me know how to connect it to azure, i already tried for rabitmq.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants