Last post Apr 05, 2006 08:32 AM by schotman1
Apr 02, 2006 02:21 PM|schotman1|LINK
I getting a lot of service unavailable errors. The application shuts down and after 5 to 10 seconds starts up again.
It happens most often during, or just after installing a module. Sometimes the install goes through completely, sometimes the application shuts down during the process (e.g. before registering the module controls). About 60% of my module installations are
successful. Some modules need 5 or 6 tries before they install successfully.
It sometimes also happens when switching from preview to edit mode or when logging in.
It is extremely unpredictable and in its current state, it is hard to present this solutions to my client.
I run DNN 3.2.2 on W2003 .NET framework 1.1, in a shared hosting environment, medium trust, with 96MB memory assigned and SQL2005 database.
Hope someone can point me in the right direction,
Apr 02, 2006 03:25 PM|J7Mitch|LINK
Apr 05, 2006 08:32 AM|schotman1|LINK
Thanks John but that's not it.
This is one of those horror stories with shared hosing. You can't see what has been installed / configured. Essentialy, one is blindfolded and if multiple issues come together, be prepared.
In IIS you can set memory limits and CPU limits. The latter was my problem. Hitting CPU limits can lead to a shutdown (and thus a service unavailable error). Hitting memory limits "only" recycles the site, hence making it slower after each recycle.
My site (application pool) hit their ceiling set for CPU usage (it is set to 20% / 5 mins.). Normally you will most likely never hit this ceiling BUT if the host setting for caching is set to NONE, you are bound to hit this ceiling, especially when setting
up the site.
For me this was a costly albeit a valuable lesson... one learns when it hurts... trust me it did.
BTW See also threads: http://forums.asp.net/thread/1224347.aspx and