During the execution of a limit load test for a client, everything happens correctly at the beginning, but NL-NETWORK-01 errors suddenly appear after a certain heavy load.
Error Code: NL-NETWORK-01
Message: Network error: An IO error occurred sending the request.
Details : java.io.EOFException: HttpConnectionOverHTTP@69ed9b49(l:/10.178.8.127:35252 <-> r:wamwg-rec.recgroupement.systeme-u.fr/10.178.xxx.xx:443,closed=false)[HttpChannelOverHTTP@174acb75(exchange=HttpExchange@2aa0a348 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@3a09a766(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@3f3b44bd{s=START}],recv=HttpReceiverOverHTTP@7eeb314c(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of 0}]]]
In a previous post on the forum dating from 2016 (http://answers.neotys.com/questions/1144936-facing-network-error-io-error-occurred-sending-request-error-single-user), the support indicated that : "It's a kind of connection reset. If it happens during a test you should check any network devices between your load generator and your application. It can be an issue due to firewall, proxy, load balancer or even the application under load."
But I would have liked to know if the analysis track was always similar or if new tracks could be evoked ? Also, I wanted to know if the cause could come from the Neoload injection infrastructure ?
I am in version 6.6.0 of Neoload and for information, I applied the setting recommended by Neoload for tests with high load (run WindowsNetworkTuning.reg and restart, etc ...). Also, a test with 4 injectors instead of 3 has to generate the same errors after exactly the same time.
Would you have a resolution track for this problem ?
Thank you very much