Hi,
I am getting following error while running the test.
Error Code: NL-RUNTIME-01 Message: Internal error occurred sending the request. See response for more details. Details: org.eclipse.jetty.client.EpochThrowable: java.net.ConnectException: Connection timed out: no further information
I checked the neoload documentation and "NL-RUNTIME-01" is mentioned as a bug there.
So please help me out in this issue.
Thanks,
Abhishek
It seems more a network issue. When do you get that error? Is it during a load testing or during a checkvu? Is it always on the same request?
What was the response of that request during the recording?
HI Nouredine,
I am getting this error in both cases, during virtual user check and load test. it seems something sporadic.
It is API testing so do not have the recorded content.
When i am doing virtual user check, sometimes it is failing because of the above mentioned error. Same with the case in load test. Sometimes i am getting this error during my load test.
When error is coming then it is coming for any request . It is not specific to request.
Thanks
If it was not sporadic i would say that that issue might with a proxy settings. Are you hitting the API directly or are you going through other network devices like proxy, Load Balancer etc...?
Also when you reproduce the issue if you look at the LG logs you should have the full stack trace of the error. It should be in the test Results section under Logs tab.
Could you provide that stack strace?
Hi Nouredine,
We are not having proxy but yes we have load balancer.
Please find the stack trace of the error:
2019/10/21 11:43:58 ERROR - neoload.HttpClient: Exception during the send org.eclipse.jetty.client.EpochThrowable: java.net.ConnectException: Connection timed out: no further information
at org.eclipse.jetty.client.HttpClient$1$1.failed(HttpClient.java:612)
at com.neotys.neoload.network.httpclient.jetty.http.CustomSelectorManager.connectionFailed(CustomSelectorManager.java:58)
at org.eclipse.jetty.io.ManagedSelector$Connect.failed(ManagedSelector.java:644)
at org.eclipse.jetty.io.ManagedSelector$Connect.access$1300(ManagedSelector.java:611)
at org.eclipse.jetty.io.ManagedSelector.processConnect(ManagedSelector.java:379)
at org.eclipse.jetty.io.ManagedSelector.access$900(ManagedSelector.java:56)
at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(ManagedSelector.java:286)
at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(ManagedSelector.java:170)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:162)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection timed out: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.eclipse.jetty.io.SelectorManager.finishConnect(SelectorManager.java:337)
at org.eclipse.jetty.io.ManagedSelector.processConnect(ManagedSelector.java:349)
... 8 more
Do you have a way to bypass your load balancer and to try from a different load generator machine?
It does not seem to be a NeoLoad issue. So the best is to modify the network path to reach your application to find the culprit. If you have a Linux machine it would be great to test with to avoid any third tools installed on your Windows machine (if it's the case) that could interfer.
