Can you post the test plan, or a minimal version, that shows the behaviour and that can be run by us (JMeter devs)?
If not, try to disable some elements of your test plan and evaluate, whether the same problem can be observed? Think of a binary search (for a bigger test plan). For example disable the lower half of the test plan and try the test, if the problem remains disable one half of the remaining test until the problem disappears. Felix Am 14.05.20 um 08:24 schrieb [email protected]: --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
