Hello guys,
I posted a similiar post concerning dotnetnuke shutting down in an earlier post and you guys told me about iis shutting down wb aps after 20 minutes or so idle time by default. This was the case and I talked to my host company at which time I set up a scheduled task via their control panel which allowed me to hit a page in my site every 15 minutes to avoid this issue.
However the issue presisted and upon talking with my host about it they suggested I look at event logs in a local installation and see what was going on. Well since I had a local installation I did check out some event logs and what I found was baffling. The app did shut down (not as much as in the production site) but their were a couple of places where it did shut down and in both instances I got the following messages:
---------------------------------------------------------------------------------------------------------------------------------------------------------------
| 2/13/2008 1:47:49 PM Application Shutting Down Shutdown Details: The AppDomain shut down because of the maximum num ... |
Shutdown Details: The AppDomain shut down because of the maximum number of dynamic recompiles of resources limit.
Server Name: Bo
| |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Very interesting message but very cryptic to me what does this error mean that the maximum number of dynamic recompiles of resources limit as a reason for the app to shut itsself down and what could be done to prevent this kind of app shutdown error from occuring and how would I go about being able to implement the solution.
I never quite so this error as a reason for shutting dotnetnuke down in my production environment but then again maybe the fact it was in a shared hosting setting I would never get this error but just simply that it was shut down do to the hosting environment. Are the host technitions correct that their might be something internally with dotnetnuke going on as to why the app recycles or shuts down or is it just that they are not wanting to tackle the issue thanks
Bo