[RESOLVED]Correlating messages (request/response) using JMS support

Hi,

Message selector is implemented in SoapUI 3.5 beta 2 in JMS Header inspector (see attachment) ,so you are probably using SoapUI 3.5 beta 1, right ?

Let us know how its works for you

regards
nebojsa
eviware.com

Hi Nebojsa,

I use beta 2 and I can use message selector but...
I have to specify in message selector something like “JMSCorrelationID =${=context.testCase.testSteps["…"].testRequest.JMSMessageID}

Response message has it’s own JMSMessageID but it contians in JMSCorrelationID the JMSMessageID of request message. So if we work with multiple threads any thread should do something like this (pseudo code):
make message
// message is at this point without JMSMessageID
send message to request queue
// after send message object gets JMSMessageID
obtain id from the message
make selector “JMSMessageID= + ‘requestMessage.JMSMessageID’
receive response using selector.

So in Soapui I must specify message selector , but I have to know message id of request. Messageid of request is know after sending request message to request queue. Property expansion can’t help here (this is my question) because property is expanded before teststep execution (so before request message is sent).

Hi,

here is how you can specify message properties

testRunner.testCase.testSteps["...."].testRequest.response.messageReceive.JMSMessageID
or
testRunner.testCase.testSteps["...."].testRequest.response.messageSend.JMSMessageID  etc.

and my suggestion is to use two JMS test steps , first for sending and second for receiving .
This way your JMSMessageID from first step can be expanded.

Let us know does this helps.

regards
nebojsa
eviware.com

Hi all,

I am new in Soapui  please can you be more specific, how correlation works. 

I try this :

1. Test Request Step with Endpoint jms://weblogic::queue_IN without any correlation in JMS Headers
2. Test Request step with Endpoint jms://weblogic::-::queue_OUT with CorrelationID = ${=context.testCase.testSteps["step1"].testRequest.response.messageSend.JMSMessageID}

One by one is OK
Load test is not OK .

Thank you

Sorry for my bad English

Hi,

correlation pattern works like this:
Set the value of JMSCorrelationID on the response to the value of JMSCorrelationID on the request before sending the JMS response to a queue. This way client that sends request will know which response message belongs to him. And that filtering is done by setting the Message selector query.

So in your case try to:

1.  Test Request Step with Endpoint jms://weblogic::queue_IN with set  JMSCorrelationID in JMS Headers to test

2.  Test Request step with Endpoint jms://weblogic::-::queue_IN with Message Selector query JMSCorrelationID = 'test'

Hope this helps

Regards
nebojsa
eviware.com

Thanks Nebojsa,

that's what I already did but. That makes two request steps. That makes it difficult to switch between http and jms. For now I found a way to make my mock available on http and jms address. I want to achieve the same with test case to easy switch between jms and http.

Your example uses two request and if we run it on http one is enough.

Maybe we should add a checkbox "Correlate Messages" to JMS Headers tab and use it in implementation of  HermesJmsRequestSendReceiveTransport in execute method. 

Hi,

thanks for your input on this.
Your idea seems logical and I will add it in our backlog.



Regards
Nebojsa
eviware.com

Hi,

here is update on this.
Use tomorrows nightly build http://www.eviware.com/nightly-builds/ and try
your use case like this:

Use one test step for send and receive, than put in message selector field
JMSMessageID = '${=context.getProperty("JMS_MESSAGE_SEND").getJMSMessageID()}'
or any other
JMSxxx = '${=context.getProperty("JMS_MESSAGE_SEND").getJMSxxx()}'


Let us know how it works for you

regrads
nebojsa
eviware.com

Hello man,

this really works good, thanks for adding this.
gr

Hi! Is there a way to correlate in the JMS Payload(Body) instead of the Headers?