cancel
Showing results for 
Search instead for 
Did you mean: 

NoHttpResponseException: $IP failed to respond

SOLVED
Highlighted
New Contributor

NoHttpResponseException: $IP failed to respond

Hey Profis 🙂 

 

i am using ReadyApi 3.0.0

i am getting "sporadically" a wired exception while sending a rest request =>

org.apache.http.NoHttpResponseException: myIP:443 failed to respond

- missing response / garbage collected -

as you can see , there is no request send al all 

 

thanks for helping me

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted
Community Leader

@Aiham :

 

I would suggest to put some wait in between the execution might be this is because of hitting the URL frequently as you are getting response for the first 2 times and not for the 3rd time.

 

Add delay step in between the execution, hope it will resolve your issue.


Click "Accept as Solution" if my answer has helped,
Remember to give "Kudos" 🙂 ↓↓↓↓↓



Thanks and Regards,
Himanshu Tayal

View solution in original post

Highlighted
Community Hero

Hey @Aiham

I concur with Himanshu. I've had this exact behaviour before. Try running your tests in parallel, you should get the same intermittent no response. The endpoint is overloaded. Depending on your technical and nonfunctional requirements you might want to mention this behaviour to the performance testers.

Ta

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta

View solution in original post

7 REPLIES 7
Highlighted
Community Hero

Hi @Aiham,

Sorry i'm a bit confused. Are you saying the request isn't generated or once you send a request the endpoint isn't responding?

If a response isn't generated intermittently then this is unlikely to be a readyapi!/soapui issue. It's far more likely to be due to your endpoint behaviour.

With this in mind, i'd suggest looking at the logging on your web/app servers as readyapi!/soapui wouldnt have any impact on whether your endpoint generates a response or not.

If it is an issue with the request not generating then id check the readyapi!, http (script if youre using them) and error logs in readyapi!

Ta

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
Highlighted
Community Leader

@Aiham :

 

Is there any kind of authentication associated with the Service which you are missing out include that authentication too, hope that will work.

 


Click "Accept as Solution" if my answer has helped,
Remember to give "Kudos" 🙂 ↓↓↓↓↓



Thanks and Regards,
Himanshu Tayal
Highlighted
New Contributor

hey @richie  thanks for your answer

i am sending the same  GET request 3 times via ReadyAPI and with a groovy script i write the request and response into a .txt file .

The first and second request have been sent succ and i got a response => also the  request and its response have been written to that generated .txt file.

 

the third request was not responded . i looked into the logs in my endpoint , there are only two requests , looks like the third request never got to the endpoint . For this third request i see just a response in the generated .txtfile like this => no request and response

Status: FAIL
Time Taken: 0
Size: 0
Timestamp: Wed Jul 15 08:48:01 CEST 2020
TestStep: Monitoring request

----------------- Messages ------------------------------
org.apache.http.NoHttpResponseException: MyIP:443 failed to respond

- missing response / garbage collected -

Looks like ReadyAPI fails to create and/or send the third request.

As i mentioned , this happens sporadically 😞

I see this error in ReadyAPI logs

 

 

2020-07-15 08:48:01,042 ERROR [errorlog] org.apache.http.NoHttpResponseException: MyIP:443 failed to respond
org.apache.http.NoHttpResponseException: MyIP:443 failed to respond
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261) ~[httpcore-4.4.3.jar:4.4.3]
	at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165) ~[httpcore-4.4.3.jar:4.4.3]
	at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:167) ~[httpclient-4.5.2.jar:4.5.2]
	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doReceiveResponse(HttpClientSupport.java:525) ~[ready-api-soapui-3.0.0.jar:3.0.0]
	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124) ~[httpcore-4.4.3.jar:4.4.3]
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[httpclient-4.5.2.jar:4.5.2]
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) ~[httpclient-4.5.2.jar:4.5.2]
	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpClient.doExecute(HttpClientSupport.java:248) ~[ready-api-soapui-3.0.0.jar:3.0.0]
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[httpclient-4.5.2.jar:4.5.2]
	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:593) ~[ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:661) ~[ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:332) ~[ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:249) ~[ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:130) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.WsdlSubmit.submitRequest(WsdlSubmit.java:89) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.support.http.HttpRequest.submit(HttpRequest.java:256) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.teststeps.HttpTestRequestStep.run(HttpTestRequestStep.java:286) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:265) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStepByName(AbstractTestCaseRunner.java:244) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.model.testsuite.TestCaseRunner$runTestStepByName$0.call(Unknown Source) [ready-api-soapui-3.0.0.jar:3.0.0]
	at Script1.run(Script1.groovy:21) [shell:?]
	at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:94) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.support.scripting.groovy.SoapUIProGroovyScriptEngineFactory$SoapUIProGroovyScriptEngine.run(SoapUIProGroovyScriptEngineFactory.java:83) [ready-api-soapui-pro-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:162) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:265) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:52) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:175) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1) [ready-api-soapui-3.0.0.jar:3.0.0]
	at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:130) [ready-api-soapui-3.0.0.jar:3.0.0]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_181]
	at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_181]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_181]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_181]
	at java.lang.Thread.run(Unknown Source) [?:1.8.0_181]

 

Highlighted
New Contributor

hey @HimanshuTayal  thanks for the answer

actually the same request have been sent 3 times , the first and second were succ , the third was failing and did not reach the endpoint

Highlighted
Community Leader

@Aiham :

 

I would suggest to put some wait in between the execution might be this is because of hitting the URL frequently as you are getting response for the first 2 times and not for the 3rd time.

 

Add delay step in between the execution, hope it will resolve your issue.


Click "Accept as Solution" if my answer has helped,
Remember to give "Kudos" 🙂 ↓↓↓↓↓



Thanks and Regards,
Himanshu Tayal

View solution in original post

Highlighted
Community Hero

Hey @Aiham

I concur with Himanshu. I've had this exact behaviour before. Try running your tests in parallel, you should get the same intermittent no response. The endpoint is overloaded. Depending on your technical and nonfunctional requirements you might want to mention this behaviour to the performance testers.

Ta

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta

View solution in original post

Highlighted
New Contributor

@richie  @HimanshuTayal  thanks, i will add a delay and check the performance of my env/server ...

 

New Here?
Join us and watch the welcome video:
Announcements
TechCorner Leaderboard
Want a fun and easy way to learn ReadyAPI and show off your skills? Try solving weekly TechCorner challenges and get into the Leaderboard!


Challenge Status

Get a full Raw JMS request

Participate!

Compare an expected JSON value and actual response in Events

Participate!

Fetch value/data from JSON response using Groovy Script

See replies!

Get data from Petstore and add it to Excel sheets

Participate!
Top Kudoed Authors