|
Mark Weaver wrote:
Heh - sounds like you need our WebQMS device
(http://webqms.highopinions.com). This resets IIS for me/reboots the
server, but does an HTTP check first, which is for those times when IIS
randomly consumes 100% CPU and serves no pages. That bug has been present
since IIS4.
I just went to this site and got this:
ALERT: Redirection limit for this URL exceeded. Unable to load requested
page.
for every link I wanted to click on that page. This is a good example of
non-returning customer. I will _never_ ever again come back to this site
because of this issue. I might have recovered by now but I don't care
anymore. See? :).
After that shameless plug ;) could you point me at the 64Mb details? I had
a go with google but was unable to find anything relating to an ASP memory
limit; presumably this is related entirely to the [VB|whatever]spit
processing?
I found some interesting pages (but not _the_ one):
http://www.windowswebsolutions.com/Articles/Index.cfm?ArticleID=8069&pg=2
http://www.asp101.com/resources/kb.asp
http://msdn.microsoft.com/msdnmag/nettop.asp?page=/msdnmag/issues/1100/GCI/GCI.asp&ad=ads.ddj.com/msdnmag/premium.htm
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q188352&;
Cheers,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
| 