JMeter-Rabbit-AMQP icon indicating copy to clipboard operation
JMeter-Rabbit-AMQP copied to clipboard

AMQP Consumer stays active for duration of Test Plan

Open PeteTh opened this issue 8 years ago • 1 comments

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 avatar Feb 13 '17 10:02 PeteTh

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

PeteTh avatar Feb 13 '17 13:02 PeteTh