Some scripts are returning this connection timed out error but there's no additional information of what can it be. Has anybody had this issue?

Hi, the test log would have more details on which request timed out.

A time out can be caused multiple ways

• under heavy load a server can't deal with the traffic anymore and takes longer and longer to respond and eventually the time to respond times out.

If you have a schedule with stages of say 100, 250, 500, 750, and 1000 users and

only starting to see timeouts with 750 users for example, it's a server capacity issue.

If the schedule has just one stage of say 1000 and we get time outs then first inclination is to blame RPT :-) So use a schedule with stages working up the user load to confirm.

• it could be the web server is actually down, does it come up in live browser?
• has the script been editted where it used to go to host abc123 using TLS 1.2 and SSL and the hostname was changed to another webserver? If that web server doesn't support TLS 1.2 then responses to our requests will time out
• Correlation issues or perhaps using an older test and the server traffic has changed may cause a timeout. The server might sense it's under attack and just ignore future incoming requests from the same IP

The good news is a connection time out is almost never RPT's fault. If we get a timeout that means we made the request. That's RPT's job. The server's job is to respond. If it doesn't in the configured amount of time we'll get a timeout for our request

Hi Paul,

Thank you for your answer. This helps. Sorry for the late response, I haven't seen the email notification.

Diego