I need some help with this error:
System.Net.Sockets.SocketException A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond example.com:80
I have hosted a website in IIS on port 80 only.
5 other sub web services are hosted and all are using the same port 80 and same app pool.
I need to understand few things as follows:
As I have several web application (a website and 5 Web Services) running, will it cause socket connection errors? if so how can I keep track of the limit of the available sockets IIS/System can handle.
Web applications will be hosted on IIS 64bit of windows server 2019 8Gib RAM, Azure D2 V2 VM. Is it a good idea?
I don't want the system to have socket exceptions because of too many concurrent connections. How to solve this problem? may be with each app in separate app pool or something?
Test Case Scenario: Website will have max 5 users only but web services will be used by 30 users and each user can fire up to 90,000 requests in a day (sometimes up to 20 concurrent request each user might fire) for a single web API. I need a way to monitor/know how many concurrent requests are possible?
Each web service call will take less than 2 seconds to complete and code is pretty good and it runs smoothly for 1000 concurrent threads no problem. I am using SOAP UI to load test the application from a PC with normal specs (dual core, 8gb ram) and if I increase the load the socket connection failures as mentioned above occurs. Where is the problem code, IIS Server level or client side?
I think the above few points will help to understand the environment these applications are running in. I would like to know some best practices to follow in such cases.