When NeoLoad sends a request and acknowledged by the server, it will wait for the response. However, in order not to wait an infinite amount of time, there's a timeout so NeoLoad can give up and raise an error. That's why you got this “Read timed out” error.
By default, during the run time, this timeout is set to 300s (5 minutes). this period of time is usually sufficient for most situations.
Nevertheless, in specific cases, you might not get any data from the server for more than 300s. In that case; here is the procedure to increase the run time timeout in NeoLoad:
Nevertheless, in specific cases, you might not get any data from the server for more than 300s. In that case; here is the procedure to increase the run time timeout in NeoLoad:
- Stop NeoLoad
- Edit <install_dir>\conf\controller.properties
- Go to the [Runtime] section and locate that key: runtime.so.timeout=300000 Change the value to 600000 to set a 600 seconds timeout (it's in milliseconds)
- Save
- Start NeoLoad
Now, NeoLoad will only alert you the timeout error if it did not receive any data after 600 seconds
In my test script I’m doing Zip Downloading in my application. The process time in the server side can take up to 4 minutes. Running a test with 20VU in 6LG's at Neoload 4.2.2
ReplyDeleteHere we Observed that 50% user are failed to download i.e 10 VU are failed every time.
Response :-
Error detected by NeoLoad
Error Code: NL-NETWORK-01
Message: Network error: An IO error occurred sending the request.
Details: java.net.SocketTimeoutException: Read timed out