I have observed sometimes I am getting 600 error code in my jmeter response. I need help what was that and what things shall we implement to avoid this?
Thanks in advance.
HTTP Status Code 600 is not something defined by the standard, you need to consult your application developers and ask them what could be the cause of it.
I can think of the following possible reasons:
It happens due to missing or improperly implemented correlation
Your application gets overloaded and cannot handle the incoming requests properly, try increasing the load gradually and try to find the relationship between the number of users/request per second and presence of this error
You can add a Listener like Simple Data Writer to store request and response details, it might be the case you're sending a malformed request and application responds with 600 status code instead of normal 4xx
Make sure to follow JMeter Best Practices as it could also be the case JMeter fails to properly send the request due to bad configuration and/or lack of resources
Related
I am using jmeter to load test a website. I have tested from 1 to 400 users. however while testing for above 500 users/threads, I am getting 401/unauthorized error for few users. Hope you'll help me to find out a solution to this problem.
I can think of 3 possible reasons:
There is a parameterization problem with your test, i.e. it sends wrong credentials, you can use i.e. Simple Data Writer configured to save requests and response data for failing requests and inspect it using View Results Tree listener.
JMeter gets overloaded and cannot properly perform correlation. In addition to point 1 check whether you're following JMeter Best Practices and ensure that JMeter has enough headroom to operate in terms of CPU, RAM, etc. using i.e. JMeter PerfMon Plugin
Your application gets overloaded and cannot handle 500+ users, check your application logs, resources usage, output of APM tools, etc.
.net application starts giving error http 400(bad request) when 200 concurrent users are loaded.
And while running script, when application is browsed manually, could able to see same errors. This basically rules out, its not client issue.
So What is causing this error?
Kindly help
We don't know but it sounds like an application bug in any case because HTTP status codes 4xx are client errors and given it occurs only under the load the application should respond with 5xx server error codes
You need to inspect your application/webserver/loadbalancer logs as most probably the cause can be figured out from them.
Also it would be a good idea to check whether your application has enough headroom to operate in terms of CPU, RAM, etc as the errors could be caused by simple lack of resources. You can use i.e. JMeter PerfMon Plugin for this
I am creating a script through Blazemeter (which storing some data in DB) and running through JMeter. Script is running fine but data is not stored in DB. What I am missing?
The chance of replaying recorded script is minimal as modern web applications widely use dynamic parameters for security reasons or client-side state tracking
Make sure to add HTTP Cookie Manager to your Test Plan
Make sure to perform correlation of any dynamic parameters
With regards to "Script is running fine" - JMeter automatically treats responses with HTTP Status Codes below 400 as successful, so "green" result doesn't necessarily mean that your script is doing what it is supposed to be doing. Try inspecting responses using View Results Tree listener, most probably you're getting stuck at login page. Going forward you can consider adding Response Assertions in order to perform extra checks against the responses.
I have a single node elastic search server running on ec2. I want to do some load testing using search requests with random search queries. I am using JMeter for load testing with two different approaches -
HTTP Client - When I test using these clients with 10k/20k/50k of requests, it works fine.
ES Transport Client - This works fine with approx 2k of requests.
Here are the steps I have followed -
Instantiating client on every run and close it once the test finished.
Once client instantiates, I start the jmeter sampling and send the search request.
After this run, stops the sampling.
I am getting No Node Available Exception after 2k of request with transport client.
ES Server is running with 3g of memory and have given 6g of memory to load tester.
Please help me if there is some config modification required and if I am not using the correct approach to test the load.
Thanks in Advance.
What kind of responses are you getting from the http test? Have you verified you are getting valid responses for all 10~50k requests? It might be perhaps your cluster cannot take on the load you're putting on it for either test. Since TransportClient is more intimately coupled to the ES server, you will explicitly see errors that come back from TransportClient, but if you're simply sending requests via HTTP without validating the response, it's easy to miss any issues.
Although, before taking a stab in the dark like I just did, I would also check to see what kind of QPS you are getting using the HTTP method vs the TC method, what your CPU/memory look like throughout both tests, what the response times look like, etc. It helps to monitor the health of your system throughout the process to detect any symptoms that might help explain the cause.
I am testing websocket server using JMeter.
With several times of trial and errors, I could run test successfully.
But I am still unable to see the response properly.
For example,
I made my server to return some specific response, when it receives the request.
However in results listener, sometimes proper response is found,
but sometimes just request string is found.
I used JMeter plugin of Kawasima
and added View Results Tree listener.
If I miss something, kindly let me know how to see the correct results.
I already checked the packets, server and jmeter properly communicated each other.
Thanks in advance.
Dongkyoung.
Can you check your play with different values of response timeout in Jmeter. I had the same issue setting different values changes the time of response.
Hope it helps.