Home > Net >  Hung on the IIS website always recycling application pool is why
Hung on the IIS website always recycling application pool is why

Time:11-18

The request from the system after hanging up will always appear hangs, is the network status, F12 bores me to death, how all don't see reason, web and database server memory and CPU are all no problem, the iis Settings is also made me very mad, light lets you set, don't allow you to view the status, problems where basic look not to come out, can recycle the application pool down

I just wonder why is normal after recovery, recovery after I watched the memory usage is the same as the original, 35% did not change, why to pool recycling program, the contents what I see

CodePudding user response:

Quote=refer to the original poster LikeWatchStar reply:)
. Why on earth to recycling pool,...


More than can the IIS service website,

An optimized logic is that if the mo site did not request for a long time, might as well put it recycling, release resources want to let other sites run better,
IIS can defend, once have new request, then reload the site, the request also can get the response,

CodePudding user response:

reference 1st floor github_36000833 response:
quote=refer to the original poster LikeWatchStar reply:]
. Why on earth to recycling pool,...


More than can the IIS service website,

An optimized logic is that if the mo site did not request for a long time, might as well put it recycling, release resources want to let other sites run better,
IIS can defend, once have new request, then reload the site, the request also can get the response,


I do want to know what caused the iis must be recovery to normal use

CodePudding user response:

Good website also can work normally without recycling,

You need to debug and find out the reason of can't work normally, such as logical deadlock, the database connection used, etc.,

CodePudding user response:

Asp.net was often can restart, iis itself also often can restart API containers process, such as 5 minutes you can configure the automatic recovery, physical memory using 80% recycled, instantly connect 200 immediately recycling, asp.net will restart when meeting serious run-time exceptions, also can put in a DLL library files in the directory is changed automatically restart, or if you modify the web. Config file even if a space is automatically restart, or you delete any other than the app_data restart when a subdirectory... Anyhow there are countless possibility caused by asp.net and iis for system maintenance and resume parsing the HTTP request API vessel process,

Many people learn asp.net didn't meet a good teacher, did not learn about asp.net compile basic principle and programming specifications, do not know something a little deeper, I don't know "Session is lost" and "InProc mode" concept, in fact, asp.net could lose all the memory state of data at any time, lost - not expired,

Asp.net programmer must learned this kind of knowledge, because from the beginning will be on the basis of such knowledge to design the asp.net application, otherwise state often encountered error, often entangled with upside down,

CodePudding user response:

But to explain, restart asp.net's just a matter of millisecond, you might find the set of all the Session data, Application data collection, memory static objects, and so on all is lost, the initialization, if you find "card dead" should be your own system died, estimation is your system to get across, not asp.net,

CodePudding user response:

Your program has collapses cause, by logging for troubleshooting
  •  Tags:  
  • C#
  • Related