Hi,
In fact the request message is being sent (pending message), but the reply queue does not seem to be consuming the message. I wonder if anyone else has experienced this?
Many Thanks
Aidy
On 7/8/2015 at 12:40 PM, adrian...@hushmail.com wrote:Hi,--I have an ActiveMQ broker which I can make a tcp connection to.I have a simulation which uses the Gatling JMS DSL.Unfortunately, the message is not sent to the queue and I get a test that loops without any requests being made.It is difficult for me to debug the test without a thrown exception and I wondered if I was doing anything obviously wrong?Many ThanksAidy--
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.
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.
Hi StephaneI've now added the matchByCorrelationID method to the JMS config and I can view the message in the web console. A response queue appears as a consumer, however the request queue does not appear to have any consumers associated with it and the message is not consumed.
Just for the archives, destination does consume the message..destination(queue("loadTestQueue")).replyDestination(queue("loadTestQueue"))Aidy
On 7/9/2015 at 5:33 PM, adrian...@hushmail.com wrote:The request and response queue are set here: https://github.com/bbc/gatling-load-tests/blob/master/src/test/scala/bbc/amq/AmqRequestResponse.scala#L21-L22.The issue can be reproduced by running:$ docker run -p 61616:61616 -p 8161:8161 cloudesire/activemqAnd changing the URL from the above simulation to the boot2docker ip.Many ThanksAidy
Yes. I am saying this. I'll create a reproducer.
> you were using different queues ("requestQueue" and "responseQueue")
My understanding of the JMS request/reply model is that there are two queues. The sender sends a message on a request queue which is processed by the receiver and a reply is sent back on the response queue which the receiver listens to. The messages are matched by JMSCorrelationID.The original commit was based on a Gatling test:Many ThanksAidy
Aidy
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
val jmsConfig = jms
.connectionFactoryName(jmsConnectionFactory)
.url(jmsUrl)
.credentials(jmsUsername,jmsPwd)
.disableAnonymousConnect
.contextFactory(classOf[org.apache.activemq.jndi.ActiveMQInitialContextFactory].getName)
.listenerCount(1)
val scn = scenario("JMS test").repeat(1) {
exec(jms("req reply testing").reqreply
.queue(jmsQname)
.textMessage("hello from gatling jms dsl")
.property("test_header", "test_value")
Aidy