Gatling not assering number of sent/recived messages in JMS

Gatling (Open-Source)
1

Below is the output from Gatling after running a test that uses both JMS and HTTP, what I dont understand is the line on JMS Load:

On 60s elapsed it says 4059 active and 1939 done with OK=1939
On 61s elapsed it says 0 active and 6000 done BUT STILL OK=1939 and KO=0

This is not the expected behavior it means that we are not fast enogh to consume the last 4061messages, why is Gatling just skipping all messages that are not delivered in time?

2016-09-14 12:38:33 60s elapsed
---- REST -----------------------------------------------------------------
[#################################################################---------] 88%
waiting: 0 / active: 54 / done:426
---- JMS Load -------------------------------------------------------------
[#######################---------------------------------------------------] 32%
waiting: 2 / active: 4059 / done:1939
---- Requests ------------------------------------------------------------------

2

Sorry, but it’s impossible to figure out your problem if you don’t provide a working sample so we can reproduce.

3

Well the issue is that gatling is not taking into account that the loadtest is building queues. So instead of saying the messages put on the queue are fail it just cancels them wich is strange.

4

That’s not something we’ve experience so far in the apps we could test against.
So it would really help if you could provide a sample app we could use the reproduce.