I'm being told by my hosting provider (they run windows server 2003)
that all hosting providers (in a shared hosting environment) have to
restart IIS one or (more often) multiple times per day usually because
of coding problems on the part of their clients. I suppose by this
they mean bad asp.net code throwing unhandled exceptions, etc. They
also say that have scheduled IIS restarts every night. I believe they
also stated that they regularly reboot their servers on some periodic
basis. I'd like to know if this is actually standard practice for
commercial hosting providers. Any information would be much
appreciated.
Thanks!
Ratatooie - 29 Dec 2005 16:27 GMT
> I'm being told by my hosting provider (they run windows server 2003)
> that all hosting providers (in a shared hosting environment) have to
[quoted text clipped - 8 lines]
>
> Thanks!
It makes sense that they are doing that. IIS doesn't behave well over the
"weeks at a time" timeframe and needs to be restarted. Likewise for Windows
itself. (Any good admin is patching the server too, and some of those
require reboots.)
Though, several times a day is excessive. If I were that host, I'd be
leaning on or kicking out the clients that were causing problems with their
code rather than just putting up with it and causing problems for other
clients. You can restart individual virtual webs separately... but wether
or not that will fix their problems depends on the problem.
So, the frequency of occurance is NOT standard. That they are doing it at
all IS standard.
@Amp@@ - 30 Dec 2005 00:13 GMT
If the hosting company utilized App Pools properly then they would not have
to do this.
> I'm being told by my hosting provider (they run windows server 2003)
> that all hosting providers (in a shared hosting environment) have to
[quoted text clipped - 8 lines]
>
> Thanks!