Forum Discussion

taibc's avatar
taibc
Occasional Contributor
6 years ago

SOAP UI doesn't show response content correctly

I am trying to use SOAP UI to test jms request, but the response content (in response panel) is the same the sent request, how can I fix this ? (I also try to add option "Add SoapAction as property" ...
  • Nastya_Khovrina's avatar
    Nastya_Khovrina
    6 years ago

    Hi taibc,

     

    As a response, you get a message which is currently in the queue. What JMS provide do you use? 

    You can monitor the queue when you run the JMS test step in SoapUI.

     

    For example, the vn.exchangerate.1.0 queue has 2 messages with:

    messageId: 1
messageId: 2

    You have this JMS test step in SoapUI:

    jms://SOA_API::queue_vn.exchangerate.1.0::queue_vn.exchangerate.1.0

     

    This test step sends a message with messageId:3 to the queue. In the response, you will see the following:

    messageId: 1

    because this message was first in this queue. And, the current queue state will be the following:

    messageId: 2
messageId: 3

    If you run the same step once again you will receive:

    messageId: 2

    The current queue state:

    messageId: 3
messageId: 3

    Finally, if you run the JMS test step one more time, you will get 

    messageId: 3

    because this message is the first in the queue.

     

    And so on...

taibc's avatar
taibc
Occasional Contributor

Nastya_Khovrina  : Thank you, I can get the response now. But, some time I got the response of previous message. Please see my image, I send the request with id 13545 but I got the response of the message 13544, if I send request a few times, I will get the response of correct message ID. I checked my webservice process (it return correctly), but I don't know why SOAPUI's response is incorrect

Nastya_Khovrina's avatar
Nastya_Khovrina
SmartBear Alumni (Retired)
6 years ago

Hi taibc,

 

As a response, you get a message which is currently in the queue. What JMS provide do you use? 

You can monitor the queue when you run the JMS test step in SoapUI.

 

For example, the vn.exchangerate.1.0 queue has 2 messages with:

messageId: 1
messageId: 2

You have this JMS test step in SoapUI:

jms://SOA_API::queue_vn.exchangerate.1.0::queue_vn.exchangerate.1.0

 

This test step sends a message with messageId:3 to the queue. In the response, you will see the following:

messageId: 1

because this message was first in this queue. And, the current queue state will be the following:

messageId: 2
messageId: 3

If you run the same step once again you will receive:

messageId: 2

The current queue state:

messageId: 3
messageId: 3

Finally, if you run the JMS test step one more time, you will get 

messageId: 3

because this message is the first in the queue.

 

And so on...

  • taibc's avatar
    taibc
    Occasional Contributor
    6 years ago

    Thank Nastya_Khovrina , I found out that: when existing pending message in queue then I got that problem. After clearing pending message, it is ok.

     

    But, when I use load test (multi thread), I also get this case, the response message is old request message, so my assertation is marked 'error'. In this case, the server hasn't process the error request yet (do not have any record in log table)

     

    How can I fix this for testing load multi threads to return correct result ?