Yes, it sounds like a custom correlation will be needed in that case. There should be a default script that gives an example and the documentation below may help.
I believe the issue with the script you initially provided is that the object being provided is a context and not the message input. I attached a text file that has the default script that shows how to access all the message parts from the context.
Hope this helps!
Yes, that roughly looks about what I believe would be expected.
It looks like a known issue, the error message was improved in the latest release to better indicate that the newer pva file is not supported by the older server. Unfortunately, the recommendation is still to use the older desktop to connect to both servers.
Update to Video https://customerportal.parasoft.com/lightningportal/s/videodetail?id=a3A4P0000047JbVUAU
Are the variables you are setting defined in your test scenario's variables section?
If not, then where are they being created?
Edit: bad resolution screenshot
Is the first screenshot the URL path as shown in the request message event? Could you share the simple pva file that you setup to debug this? I suspect there is something going on with either the settings in the pva file or a mismatch between the expected request and the actual request.
This error is coming from Oracle's JDBC driver.
Maybe try using a newer JDBC driver?https://search.maven.org/search?q=g:com.oracle.database.jdbc
I also find some things online if I search that particular error message:https://support.oracle.com/knowledge/Middleware/731983_1.htmlhttps://stackoverflow.com/questions/37323204/why-do-i-have-checksum-fail-on-every-bad-sql-request-in-oracle-when-native-enc
There was an improvement made to how the server would handle performance delays so that they could be processed asynchronously which frees up the worker threads so that they don't become blocked by performance delays. I can't find the release notes for when it was specifically added but the latest release, 2020.2, certainly includes the change.
I don't have an example, but a similar question was posted recently:Compare datasource(expected data) with actual data in the database
In Virtualize the way a data source works is that an incoming request message is correlated to a specific data source row. Then the response will use that specific row when resolving variables. To be able to correlate the incoming message to a row in the data source the responder must be configured with "Data Source Correlation" settings, otherwise it may always use the first row.
Here are two links, the first is to the documentation about configuring responders in general and the second link is to the specific section about data source correlations.
Documentation about responder correlationshttps://docs.parasoft.com/display/SOAVIRT9103CTP310/Configuring+Responder+Correlations
Documentation about data source correlationshttps://docs.parasoft.com/display/SOAVIRT9103CTP310/Configuring+Responder+Correlations#ConfiguringResponderCorrelations-DataSourceCorrelation