You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While recording the scenario with bzm correlation recorder plugin, requests are not captured in the expected order.
For example:
The expected order is:
request1
request2
request3(values passed in this request depends on the response of request1)
Order obtained is:
request3(values passed in this request depends on the response of request1)
request2
request1
Since request1 is captured only after request3, the autocorrelation is not working at this point.
But when used with HTTPS Test script recorder, request are captured in the expected order.
It would be time-saving if this issue is resolved. Kindly do the needful.
Environment
Let us know in which versions of these tools the error occurs:
JMeter's version: v5.4.1
Correlation Recorder's version: v1.2
Plugin Manager's version: v1.6
Protocol Information: Mendix Platform
Expected behavior
The expected order is:
request1
request2
request3(values passed in this request depends on the response of request1)
Please refer to previous occurrence of this same issue, in ticket "Requests are delayed while recording #22"
The text was updated successfully, but these errors were encountered:
Thanks for taking the time to report this issue, we really appreciate it!
We are aware of this behavior for JMeter versions 5.4 and later, and we will release a new version with a fix in the near future.
In the meanwhile, we usually recommend, until this issue is fixed, that you use JMeter 5.2.1 or 5.3 to avoid this inconvenience. Is that an option for you?
Regarding issue #22, the JMeter version was 5.1.1, and when version v1.2 of the Correlation Recorder Plugin was released, it appears it didn't present more inconveniences, as far as the user reported.
Hope this helps and, when we fix that issue, I'll come and let you know, so you can try it out.
Describe the bug
While recording the scenario with bzm correlation recorder plugin, requests are not captured in the expected order.
For example:
The expected order is:
Order obtained is:
Since request1 is captured only after request3, the autocorrelation is not working at this point.
But when used with HTTPS Test script recorder, request are captured in the expected order.
It would be time-saving if this issue is resolved. Kindly do the needful.
Environment
Let us know in which versions of these tools the error occurs:
Expected behavior
The expected order is:
Please refer to previous occurrence of this same issue, in ticket "Requests are delayed while recording #22"
The text was updated successfully, but these errors were encountered: