Data driven virtual service returns incorrect/cached response

Document ID : KB000073087
Last Modified Date : 29/03/2019
Show Technical Document Details
Issue:
Receiving incorrect responses for most of the transactions sent to the data-driven virtual service.
When the virtual service is deployed, the first response is correct.
For the second transaction, the value of the previous transaction is returned.
If the same request is sent more than once, then we get a valid response

For example, Excel has the data like below: 

Row 1: Column A -“ReqId=1212”, Column B – “ReqNumber=TEST{{ReqId}}”, Column C – “RequestContact=James”
Row 2: Column A -“ReqId=1313”, Column B – “ReqNumber=TEST{{ReqId}}”, Column C – “RequestContact=Joe” 
Row 3: Column A -“ReqId=1414”, Column B – “ReqNumber=TEST{{ReqId}}”, Column C – “RequestContact=Chris” 
Row 4: Column A -“ReqId=1515”, Column B – “ReqNumber=TEST{{ReqId}}”, Column C – “RequestContact=Bob” 
Row 5: Column A -“ReqId=1616”, Column B – “ReqNumber=TEST{{ReqId}}”, Column C – “RequestContact=Chris” 

When the virtual service is first deployed the first response will be correct.
If the first request is sent with ReqId=1212, the VS returns the correct response for ReqNumber=TEST1212.
When the second request is sent with ReqId=1414, VS returns response for ReqNumber=TEST1212.
When the third request is sent with ReqId=1313, VS returns response for ReqNumber=TEST1414.
If the 4th request is sent with the same ReqId value, ReqId=1313, then VS will return the valid response for ReqNumber=TEST1313.
 
Environment:
DevTest on release 10.1 and 10.2.
Cause:
There is an issue with DevTest when the dataset cell is a property itself or is has an inner property.
Example: The data set has a column {{response}} which has an inner property {{name}}. Which is a cell in the dataset being used with the VSM.
Resolution:
If you believe you are facing this issue, please open a support ticket and reference DE341863 and DE411814.
We will be happy to provide you a patch if it matches your issue.