You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2022/07/05 06:50:05 UTC
[Bug 66162] New: JMeter kills threads abruptly
https://bz.apache.org/bugzilla/show_bug.cgi?id=66162
Bug ID: 66162
Summary: JMeter kills threads abruptly
Product: JMeter
Version: 5.4.3
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: nsravanthk@gmail.com
Target Milestone: JMETER_5.5
I have a testPlan that has several transaction controllers and each one has one
or many HTTP samplers.
The problem I'm facing is that once the test duration is over, Jmeter kills all
the threads and does not take into consideration if the threads are in the
middle of a transaction controller flow or not.
On some of these transaction controllers, I do some important stuff that needs
to be done before the user logs in again, otherwise the next iterations (new
test run) will fail.
The question is:
Is there a way to tell to JMeter that it needs to wait every thread reach the
end of its flow/TransactionController before killing it?
Thanks in advance!
--
You are receiving this mail because:
You are the assignee for the bug.