Multiple (not so smartly implemented) web apps return a 200 code for redirect pages containing the stacktrace for the previous request that triggered a 500 response code. Which is why your assertions will fail.
You need to account for this possibility and make sure that you verify that you end up on the page you think you should be before attempting the extraction, not just assume that you got there solely based on the response code. Set the test plan to a "functional test mode" by testing just one active thread, use a View Results Tree (which you should remember to disable when switching back to performance testing mode as it uses a lot of memory) and in that listener check the complete set of redirection requests and their responses. That should allow you to understand what happens during most of your tests. Essentially, please learn to debug your own tests just like you would expect a developer to debug their code whenever you report a bug that they don't think should be possible. This will also allow you to get more information about what went wrong. -A On Tue, Apr 23, 2024 at 8:21 AM Sumit Kishore <sumitkishore2...@gmail.com> wrote: > > In Jmeter, requests after multiple retries are getting Response code > 200/201, however its Regular expression extractor fails to capture value. > > And because of that the next request is failing because of correlation. > > And the same Extractor works if we get response code 200/201 in 1st Go. > It's just that after multiple retries, even if the request is getting the > correct response code, it's failing to extract the value. > > Regards, > Sumit Kishore --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
