Bug 64923 - Need ability to re-execute current sampler
Summary: Need ability to re-execute current sampler
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 5.2.1
Hardware: PC Mac OS X 10.1
: P2 enhancement (vote)
Target Milestone: JMETER_5.4
Assignee: JMeter issues mailing list
Depends on:
Reported: 2020-11-14 22:04 UTC by Vinod Seraphin
Modified: 2020-11-14 22:04 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Vinod Seraphin 2020-11-14 22:04:02 UTC
To properly simulate OAuth tokens expiring and being refreshed, need the ability within a Groovy post processor to do the following when the response status is a 401:
* Invoke a HTTP transaction to obtain the updated token (would be great if this could be done by dispatching off to another sampler, but it can also be achieved by using URLConnection)
* Re-execute the current HTTP sampler with the updated Authorization token

There is no current way to re-execute the current sampler from within the Groovy post procesor.

There is also no way to have a pre-processor not fire the current transaction and just skip/continue to the next sampler or to the start of the current loop.
Comment 1 The ASF infrastructure team 2022-09-24 20:38:21 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5434