When executing your JMeter test script via Blazemeter, you may find that the test encounters a number of HTTP 500 errors in response to some of your samplers, which will appear under the Errors tab of your report.
HTTP 500 literally means "internal server error". This is a generic code that requires investigating in your application server itself to troubleshoot. On the Blazemeter side, your server does not send us any additional information by which to know why it sent a 500 code.
This error code usually does not point to a problem with Blazemeter, but to a scripting problem. We recommend investigating this problem two ways:
- Ensure your script can run in your local JMeter environment prior to running through Blazemeter.
- Investigate your application server, starting with your application server's logs, to see why your server chose to return 500 codes during the timeframe of the test.