Figured out - the behavior was caused by the use of the HTTP Cache Manager and
NOT updating the time stamp with the request. By default, the cache manager has
the "Use Cache Control/Expires header when processing GET requests" enabled,
which means, if the script makes the exact same request again before the cache
expires, the request will NOT be sent to the server. In my case, there is a
timestamp parameter goes with the request, once that's set anew per iteration,
JMeter treats it as a different request and sends to the server accordingly.
On Wednesday, July 6, 2022 at 08:14:02 PM EDT, Jun Zhuang
<[email protected]> wrote:
Hi,
I am scratching my head trying to understand a strange JMeter behavior - maybe
it's something strange I did in my script - I wonder if someone can help me
make sense? I am using the latest version of JMeter.
Following is my script. The thread group has 5 threads. All the throughput
controllers have 100% setting. The strange behaviors I have been observing
(from multiple runs) are:
1. in the output, "Transaction: Navigate to Pending GDA Review" showed 5 x
iteration number times. Same for two requests inside the transaction (GET
/signalr/hubs and /GET /siginalr/negotiate) but the 1st request (GET
/Home/PendingGDAReview) only showed 5 times;
2. The "Get /Home/GetPendingGDAReviewGridData - No Search critera" request
inside the "Throughput Controller: Search without batch or LIMS ID" showed 5
times only.
The execution count for requests inside the once only controller was the
expected 5 and requests within the if controller were executed as expected.
Thanks,Jun
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
