![]() In contrast, if the percentage of errors is lower and happens at different times in your test, this is more likely your server’s inability to handle the amount of load.So how can you tell if it’s a server or a network issue? This error most likely indicates that your target server or network device has become overloaded.The closer to 100% - this is a sign that it’s your network (e.g., firewall issue). So, in essence, your load generator sent the request(s), and something got in the way of the traffic. ![]() Typically, the remote host cannot be reached because of an intervening firewall or if an intermediate router is down. Signals that an error occurred while attempting to connect a socket to a remote address and port. Using one or a combination of the solutions provided will help you troubleshoot in hopes that you achieve a quick resolution. Frontend server issues with the number of connections (IIS/Apache) or thread pool limits (Tomcat).Backend server issues (like database or resource server).Since there are several reasons for NL-NETWORK-01 errors, we need to focus on examples like: The following article serves as a best practice guide for you to attempt to resolve on your own. Typically NL-NETWORK-01 errors occur when your server fails to respond with the expected result that Tricentis NeoLoad is waiting for.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |