| Q: | Why doesn't my test stop when the "Stop user run when assertions fail" option is selected? |
| A: | This option stops the virtual user, not the test currently being run. The halted user will be replaced by a new user that will start the scenario from the beginning, in order to maintain the required load. |
| Q: | My system has memory available, so why does NeoLoad say that all available memory is used? |
| A: | The memory displayed in the Runtime panel refers to the Java heap, not to system memory. To generate heavy loads, increase the memory available to the load generator (see the section called “Increasing Available Memory for Load Generators”) |
| Q: | When checking my virtual users, why do I get an NL-NETWORK-03 error? |
| A: | The virtual user activity has been recorded correctly and you get an NL-NETWORK-03 error with the message "Failed to connect to the server". This indicates that NeoLoad couldn't connect to the server when playing the scenario. If the error details are "java.net.ConnectException: Connection timed out: connect", it probably means that the load generator is using an inappropriate network interface. Check the load generator's settings in the "Runtime/Scenario" section to make sure that the selected network interface allows connection to the web server. The most common causes of other errors are:
If the error is not due to one of these points, please carry out a short recording on a public Internet web site, such as http://www.google.com, create a virtual user and check its validity with NeoLoad. Then send the log files to Neotys Support (all the files in the <NeoLoad>/logs directory). |
| Q: | Why do some requests return a 404 error? |
| A: | If, during the test, you get 404 errors on images or JavaScript or CSS files, it indicates that the files are referenced and used in the HTML page, but are missing on the server. The final user usually doesn't notice that these files are missing because the browser ignores this type of error. Either make corrections to the application (add the missing files or delete the reference to them in the web page), delete the request from the virtual user or set the option to smart-ignore 404 error codes: see the section called “Error handling”. |
| Q: | What is an NL-REDIRECT-03? |
| A: | This means that NeoLoad couldn't follow the redirect directive in the previous request (302 Moved Temporarily). The previous request did not issue a redirect (not 302 status). The request is an "HTTP Redirect" type within NeoLoad. This indicates that the request must follow the redirect directive in the previous request. The redirect is valid if the previous request contains HTTP return code 301, 302, 303 or 307, and also contains a response header named "Location". The NL-REDIRECT-03 error indicates that the previous request (the "referrer") did not contain HTTP return code 301, 302, 303 or 307. To begin with, check the validity of the request's referrer:
Click on the request's " Then investigate the reason(s) why the referrer didn't return the expected HTTP code. Typically, the reason is that the request was played with an invalid parameter and generated an HTTP 200 error code or generated an unexpected HTML content. See the question "Why doesn't the virtual user behave as expected?". |
| Q: | Why do my pages return "java.net.NoRouteToHostException"? |
| A: | The "java.net.NoRouteToHostException: No route to host:connect" probably means that an inappropriate network interface is being used. Check the load generator's network parameters (see the section called “Load Generator Hosts”) |