Incorrect error message displayed 500 internal server error instead of "Http 429 Too Many Requests" on exceeding requests per second

[asfimport]

Madhu kosireddi (Bug 63929): Stress tests-Jmeter:

We are trying to simulate more than 25 requests per second for Mulesoft API, Jmeter should display "429 Too Many Requests" however "internal server error" is displayed on increasing the load.

On updating the settings(Mulesoft limit) to 8 requests per sec, we could replicate the error at 9 requests per sec(Not consistent).

Please provide a resolution for the same to conduct Stress tests at various loads like 15 rps, 25 rps and 30 rps and see 429 Too Many Requests error while exceeding the breakpoint.

Severity: normal OS: All

[asfimport]

@pmouawad (migrated from Bugzilla): Hello, JMeter returns what the server returns. So most probably the server returned 500 not 429

1/ To check that, run jmeter test and when you reach the limit , use browser to check error code returned.

2/ Also, a simple example of your test wpuld help. 3/Are you using Embedded resources download, I don’t think so as it’s not useful for API, but double checking.

Regards

[asfimport]

@pmouawad (migrated from Bugzilla): Hello, JMeter returns what the server returns. So most probably the server returned 500 not 429

1/ To check that, run jmeter test and when you reach the limit , use browser to check error code returned.

2/ Also, a simple example of your test wpuld help. 3/Are you using Embedded resources download, I don’t think so as it’s not useful for API, but double checking.

Regards

[asfimport]

Madhu kosireddi (migrated from Bugzilla): Hi,

Thanks for the response, appreciate it. I will not be able to share the Json but it has 30-35 key value and no data types. We are trying to start tests from 5 users, no ctt and gradually incresing the users to 7, 9, 11.. to see the breakpoint/max concurrent users per sec. We are conducting 30 minute tests to see for 429 response atleast for few of the requests. Please suggest on best practices to conduct capacity tests in Jmeter 5 version.

[asfimport]

Madhu kosireddi (migrated from Bugzilla): Developement have configured proper error messages for each failure request from Mulesoft API. We are getting internal server 500 and Gateway Timeout 504 errors. Please advice.

[asfimport]

@pmouawad (migrated from Bugzilla): Hello, Surely it's not JMeter which creates those response codes. I cannot help with such details, and I don't think issue is in JMeter.

For other questions, please use mailing list. Closing bug as INVALID. Thank you