D
dbeavon
Guest
I'm pretty convinced that I ran out of memory because of a flurry of PASOE activity. It was probably a self-inflicted problem that occurred because of a client program that was making an unreasonable number of concurrent connections (possibly over 100). But I hadn't ever seen the error message before, and I didn't know if the scope of the memory leak was local to a session, an ms-agent process, or the entire server. I suspect it was the entire server. But as soon as I was able to start doing some investigation, the problem had already cleared itself out. I have a pretty good idea about which client program was responsible, and if changing the behavior of that program doesn't work then I will enable a higher level of logging in ASPlumbing, and start monitoring the Windows memory perf counters. Thanks, David
Continue reading...
Continue reading...