Search code examples
concurrencyjmeterperformance-testing

Concurrency Issue not Recreatable through a JMeter Script

Development analysis had revealed that a certain issue had occurred due to two concurrent user requests being executed in the server. However, when the same was performed using a JMeter script with two threads(users), the issue did not get reproduced despite both threads being synchronized using a synchronization timer for the save method request and the listeners indicating that both response times of the threads were the same for that particular request.

What could be the potential cause of this observation? and could there be suggestions to improve the test to either disprove or prove this claim in a better way?

Solution

  • I can come up with the following assumptions:

    1. The analysis result is not correct
    2. The analysis result is correct but the issue is intermittent or Heizenbug-like
    3. You're not sending "the same" request using JMeter, maybe the payload is incorrect or you miss a header. If it's possible to obtain a network footprint of the issue in form of i.e. .pcap or .har file you could compare it with the network footprint produced by JMeter