This can be accomplished by making an edit to two different core NeoLoad files: Change the NeoLoad port: Another option is to change the default port of the NeoLoad load generator to something other than 7100.Click Refresh, and NeoLoad will use its ability to search for load generators and will put the localhost:7100 back on the list.Remove the localhost load generator, add back in: A different approach could be to select the localhost:7100 load generator (“Runtime” and delete it).Refresh the localhost load generator: An easy way to re-connect to your localhost load generator is to click “Refresh” in the “Runtime” section of NeoLoad.netstat -na | find “7100” > 7100.txt (Find the PID for port 7100 and then kill this process to see if NeoLoad now functions properly.): netstat -aon | find “7100” > 7100.txt.To better understand if it is an antivirus suite or firewall rule, open a command prompt and run a netstat command to find the process ID (PID) that could be using the same port as that of the NeoLoad load generator (7100). An antivirus suite or firewall rule could be the cause of this issue. If it’s intermittent, it might be something else running that’s taking over port 7100 on your computer. Eliminate a conflicting process: The first question is whether this problem happens intermittently or reliably.This article provides best practices and serves as guidance for you to attempt to resolve this issue. During your load test, you may experience issues of having your load generator localhost:7100 become unavailable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |