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

AMQP Consumer stays active for duration of Test Plan #39

Open
PeteTh opened this issue Feb 13, 2017 · 1 comment
Open

AMQP Consumer stays active for duration of Test Plan #39

PeteTh opened this issue Feb 13, 2017 · 1 comment

Comments

@PeteTh
Copy link

PeteTh commented Feb 13, 2017

Using the AMQP Consumer, I'm finding that this works great if the JMeter test plan only does one thing e.g.

Success Test

  1. AMQP Publish - sends good message
  2. AMQP Consumer - on a response queue with assertions for response message contents containing 'SUCCESS'

However if I then use a JMeter Simple Controller to group the above into a 'Success Test' then
create a second Simple Controller for 'Failure Test' that does the same only sends in a bad message.

Failure Test
3) AMQP Publish - bad message
4) AMQP Consumer on a response queue with assertions for response message containing 'FAILURE'.

Step 4 never gets the response message. That's because the AMQP Consumer from 2) is still active and there ends up being 2 consumers for the queue.

The above was all under ONE thread group, and executes serially.

So wondering how to get around this ?
How do I stop the first consumer ?

@PeteTh
Copy link
Author

PeteTh commented Feb 13, 2017

Looks like a workaround is to use a separate ThreadGroup for each Test Suite (rather than a Simple Controller), then to also choose 'Run Thread Groups consecutively' to stop them running in parallel

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

1 participant