Skip to main content

JMeter Target Server Failed to Respond Error Troubleshooting

Since JMeter version 2.10, there is an increased occurrence of NoHttpResponseException error. Due to this error, JMeter sometimes returns the dreaded ‘Target Server Failed to Respond’ message. In this tutorial we will list out some simple steps to troubleshoot JMeter Target Server Failed to Respond error.
Let’s have a look at what may be causing this issue. As per JMeter Wiki:
The increase of this type of errors can be explained by two settings changes:
  • retry of failing request (idempotent ones only) has been disabled in JMeter 2.10
  • stale check in HTTP Client 3 and 4 implementations has been disabled in JMeter 2.11
Below are some simple steps you can take to prevent this error from happening.
  • Enabling Retry: Navigate to JMeter installation’s bin directory. Edit jmeter.properties file. Uncomment httpclient4.retrycount property by removing # sign before it and set its value to 1. Apply the same changes to httpclient3.retrycount property as well. Depending on your JMeter version, these parameters may be located in user.properties file of JMeter installation.
  • Enabling Stale Check: Uncomment hc.parameters.file=hc.parameters property in jmeter.properties file and save it. Now, open httpclient.parameters file and set http.connection.stalecheck$Boolean=true. Depending on your JMeter version, httpclient.parameters file may be there in your JMeter installation as hc.parameters.
  • Disable KeepAlive: If above two steps didn’t work for you, try unchecking ‘Use KeepAlive’ flag of your HTTP requests. This is because your web application server may be failing to send the KeepAlive header. Upon not finding it, JMeter may be throwing an error.
We hope the above steps helped you in resolving the JMeter Target Server Failed to Respond Error. Let us know if it works for you or let us know if you have any other solution for this error.
Labels:

Comments

Post a Comment

Popular posts from this blog

Performance Testing in the Cloud with JMeter & AWS

JMeter is a wonderful tool  to stress test your website and  your application architecture , however if you are trying to simulate many users (>1000) one JMeter instance (=pc) will not be sufficient. You will have to set up a JMeter cluster with multiple machines. JMeter is capable or running  distributed tests , but it comes with limitations. Since most of us don’t have multiple servers laying around somewhere, we usually go to cloud service providers like  AWS , spin up a couple of  EC2 instances  and turn them off whenever we’re done. Here is the problem, JMeter uses  Java RMI (Remote Method Invocation)  to communicate to its slaves, but these connections require all machines to be on the same subnet and this is not feasible with EC2 instances. Below, I explain how to get around this problem using a 3 node configuration in AWS to execute tests. I assume that you have a written the test already and have the .jmx file r...
Post a Comment
Read more

JMeter Exceeded Maximum Number of Redirects Error Solution

While running performance test, JMeter allows maximum 5 redirects by default. However, if your system demands more than 5 redirects, it may result in JMeter exceeded maximum number of redirects error. In this post, we have listed down steps to overcome this error. Actual error in JMeter: Response code: “Non HTTP response code: java.io.IOException” Response message: “Non HTTP response message: Exceeded maximum number of redirects: 5” This error is noticed because  JMeter  allows maximum 5 redirects by default and your system may be using more than 5 redirects. You need to increase this count to more than 5 in jmeter.properties file. Follow below steps to achieve this. Navigate to /bin directory of your JMeter installation. Locate jmeter.properties file and open it in any editor. Search for “httpsampler.max_redirects” property in opened file. Uncomment the above property by removing # before it. Change to value to more than 5 Eg. 20. Save the file and restart JMet...
Post a Comment
Read more

SSO with SAML login scenario in JMeter

SAML(Security Assertion Markup Language) is increasingly being used to perform single sign-on(SSO) operations. As WikiPedia puts it, SAML is an XML-based open standard data format for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider. With the rise in use of SAML in web applications, we may need to handle this in JMeter. This step-by-step tutorial shows SAML JMeter scenario to perform login operation. First request from JMeter is a GET request to fetch Login page. We need to fetch two values ‘SAMLRequest’ and ‘RelayState’ from the Login page response data. We can do this by using  Regular Expression Extractor . These two values need to be sent in POST request to service provider. Refer below image to see how to do this. We will get an HTML login page as a response to the request sent in 1st step. We need to fetch values of some hidden elements to pass it in the next request. We...
Post a Comment
Read more