Last post May 27, 2005 06:54 AM by mark_richman
Feb 25, 2005 04:12 PMfirstname.lastname@example.org|LINK
Feb 27, 2005 09:58 PM|qbernard|LINK
Feb 28, 2005 02:54 AM|klevereblog|LINK
Feb 28, 2005 07:53 PM|mark_richman|LINK
Mar 14, 2005 11:27 PM|qbernard|LINK
Mar 15, 2005 06:54 AM|mark_richman|LINK
Mar 16, 2005 01:24 AM|qbernard|LINK
Mar 16, 2005 04:53 PM|klevereblog|LINK
Mar 16, 2005 07:55 PM|qbernard|LINK
Mar 29, 2005 09:38 PM|klevereblog|LINK
Mar 30, 2005 07:41 PM|qbernard|LINK
Thank you and cheers.
May 27, 2005 04:36 AM|romancehack|LINK
I faced the same problem of the iis Restart!!! and solved by knowing which site casuing the problem and fix its code,,,,,
the problem is that some of the asp pages requires a sql connection or some strange things, and if the code opens sql connections without closing them, it will casue this hang,,, and the solution is to reset the iis,,,,,,
my advice is to review the code hosted in your iis, to protect it from the DoS.....
isolating each web site in its app pool is not a solution for a hoster,,, becasue each pool will require resources and if this is the case then each iis can host 3 web sites and thats it :D,,, nono,,, think of isolating the most heavely sites in its app
pool and keep them away from other static or safe web sites,,,, and my advice also is to create 3 app pools called
1- Static: that will host all the static pages only
2-Untrusted sites: when you host a new site move it to this app pool for a month to test it and then once certified move it to the trusted app pool.
3-trusted sites: that will host your trusted tested sites....
you can have the 3.5 version,,, it will addresds some issues for the scalability and security things
May 27, 2005 06:54 AM|mark_richman|LINK