You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by "CatPrincess69 (via GitHub)" <gi...@apache.org> on 2025/05/12 07:41:27 UTC
[I] When the life of a thread expires, the requests inside are terminated halfway. [jmeter]
CatPrincess69 opened a new issue, #6455:
URL: https://github.com/apache/jmeter/issues/6455
When the life of a thread expires, the requests inside are terminated halfway.
I have a thread that runs for 1 minute
There is a transaction controller inside it and inside it there are 5 requests that are executed sequentially
From creating an entity to deleting it. The problem is that as soon as the time runs out, the thread is killed and the CRUD cycle for the entity is terminated halfway. How can I make the thread work in time and at the same time if the thread has already started working, then after the time has elapsed, it simply performs all its operations inside until the end
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] When the life of a thread expires, the requests inside are terminated halfway. [jmeter]
Posted by "vlsi (via GitHub)" <gi...@apache.org>.
vlsi commented on issue #6455:
URL: https://github.com/apache/jmeter/issues/6455#issuecomment-2872633633
There's a catch on what to do when the time runs out.
There's a workaround if you use [Open Model Thread Group](https://jmeter.apache.org/usermanual/component_reference.html#Open_Model_Thread_Group): you could add `pause(2 min)` at the end of the schedule, so it would allow thread to complete before forcefully interrupting them.
----
We could consider adding a "non-interruptible" controller which would allow users to protect a part of a test plan from interrupting, however, we can't let it hang indefinitely, so it should have a timeout so it still terminates sooner or later.
----
A similar option would be having "cleanup" actions which would execute when an operation fails:
* https://github.com/apache/jmeter/issues/4612
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org