Gatling JMS Getting java.lang.InterruptedException from JmsReqReplyAction after simulation is finished and the test doesn't stop and is trying to receive messages in a loop

[Patrik Mihalčin]

Hi everybody,

I am using Gatling JMS to test the application which uses ActiveMQ as MOM broker

I am facing issue where the scenario below:

  val scn = scenario("jms test scenario").repeat(1) {

    exec(

      jms("jms req")

        .reqreply

        .queue("requestQueue")

        .replyQueue("replyQueue")

        .textMessage("test")

    )

  }

Executes successfully with generated report at the end, but I am getting java.lang.InterruptedException in JmsReqReplyAction 

Simulation finished

14:57:21.191 [ERROR] i.g.j.JmsReqReplyAction - java.lang.InterruptedException

14:57:21.192 [DEBUG] o.a.a.ActiveMQMessageConsumer - remove: ID:N0919-59178-1459429039164-1:1:2:1, lastDeliveredSequenceId:153

14:57:21.194 [TRACE] o.a.a.t.PooledTaskRunner - Shutdown timeout: org.apache.activemq.ActiveMQSessionExecutor@662db7e0 task: {}

Parsing log file(s)...

Parsing log file(s) done

Generating reports...

================================================================================

---- Global Information --------------------------------------------------------

> request count                                          1 (OK=1      KO=0     )

> min response time                                   1826 (OK=1826   KO=-     )

> max response time                                   1826 (OK=1826   KO=-     )

> mean response time                                  1826 (OK=1826   KO=-     )

> std deviation                                          0 (OK=0      KO=-     )

> response time 50th percentile                       1826 (OK=1826   KO=-     )

> response time 75th percentile                       1826 (OK=1826   KO=-     )

> mean requests/sec                                  0.481 (OK=0.481  KO=-     )

---- Response Time Distribution ------------------------------------------------

> t < 800 ms                                             0 (  0%)

> 800 ms < t < 1200 ms                                   0 (  0%)

> t > 1200 ms                                            1 (100%)

> failed                                                 0 (  0%)

================================================================================

which results in loop of write checkers and receive in progress messages in AbstractInactivityMonitor class (activemq-core)

14:57:29.282 [TRACE] o.a.a.t.AbstractInactivityMonitor - tcp://dockermachine/192.168.99.100:32776@59179 message sent since last write check, resetting flag

14:57:29.282 [TRACE] o.a.a.t.AbstractInactivityMonitor - A receive is in progress

14:57:39.283 [DEBUG] o.a.a.t.AbstractInactivityMonitor - WriteChecker 10001 ms elapsed since last write check.

14:57:39.284 [TRACE] o.a.a.t.AbstractInactivityMonitor - tcp://dockermachine/192.168.99.100:32776@59179 no message sent since last write check, sending a KeepAliveInfo

14:57:39.287 [DEBUG] o.a.a.t.AbstractInactivityMonitor - Running WriteCheck[tcp://192.168.99.100:32776]

14:57:49.285 [DEBUG] o.a.a.t.AbstractInactivityMonitor - WriteChecker 10002 ms elapsed since last write check.

14:57:49.285 [TRACE] o.a.a.t.AbstractInactivityMonitor - tcp://dockermachine/192.168.99.100:32776@59179 no message sent since last write check, sending a KeepAliveInfo

14:57:49.285 [DEBUG] o.a.a.t.AbstractInactivityMonitor - Running WriteCheck[tcp://192.168.99.100:32776]

14:57:59.285 [DEBUG] o.a.a.t.AbstractInactivityMonitor - 30003 ms elapsed since last read check.

14:57:59.285 [TRACE] o.a.a.t.AbstractInactivityMonitor - A receive is in progress

14:57:59.286 [DEBUG] o.a.a.t.AbstractInactivityMonitor - WriteChecker 10001 ms elapsed since last write check.

14:57:59.286 [TRACE] o.a.a.t.AbstractInactivityMonitor - tcp://dockermachine/192.168.99.100:32776@59179 no message sent since last write check, sending a KeepAliveInfo

14:57:59.287 [DEBUG] o.a.a.t.AbstractInactivityMonitor - Running WriteCheck[tcp://192.168.99.100:32776]

14:58:09.287 [DEBUG] o.a.a.t.AbstractInactivityMonitor - WriteChecker 10001 ms elapsed since last write check.

14:58:09.288 [TRACE] o.a.a.t.AbstractInactivityMonitor - tcp://dockermachine/192.168.99.100:32776@59179 no message sent since last write check, sending a KeepAliveInfo

14:58:09.288 [DEBUG] o.a.a.t.AbstractInactivityMonitor - Running WriteCheck[tcp://192.168.99.100:32776]

14:58:19.288 [DEBUG] o.a.a.t.AbstractInactivityMonitor - WriteChecker 10001 ms elapsed since last write check.

14:58:19.289 [TRACE] o.a.a.t.AbstractInactivityMonitor - tcp://dockermachine/192.168.99.100:32776@59179 no message sent since last write check, sending a KeepAliveInfo

14:58:19.289 [DEBUG] o.a.a.t.AbstractInactivityMonitor - Running WriteCheck[tcp://192.168.99.100:32776]

14:58:29.288 [DEBUG] o.a.a.t.AbstractInactivityMonitor - 30003 ms elapsed since last read check.

...

Any ideas why it does not exit in normal way, but keep spinning?

[Stéphane LANDELLE]

Please provide a reproducer (scenario + JMS app) so we can investigate.

Stéphane Landelle

GatlingCorp CEO

slan...@gatling.io

--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.