Good day,
For my project I have some JMS load tests. Although the JMS test runs “fine” I’ve noticed that all the tests take longer and longer to run. After a little researching i found that the source of the problem is that Gatling does not remove the message that are put on the out queue. After clearing the out queue, the performance was reset. But the test still takes longer to run, after each run of the simulation.
Is there a way for Gatling to remove a JMS message from the queue after the message was selected with the “selector” and verified with the "check(jmsproperty())?
For illustration I made this mock execution:
.exec(
jms(“Mock scenario”)
.requestReply
.queue(ORACLE_IN_QUE)
.replyQueue(ORACLE_OUT_QUE)
.textMessage(someTextMessage)
.selector(“A selection’”)
.check(jmsProperty(“some field”, “some value”))
)
With kind regards,
Wouter Dekker