The Case in the Corner Series: Session Pool Exhaustion

re: The Case in the Corner Series: Session Pool Exhaustion

WayneM33 — Thu, 15 Jul 2010 22:51:24 GMT

@ Chris Knight - in regards to resource bottlenecks x64 bit solves most of the resource bottlenecks that were existent in 2003/xp even Vista 32 bit now has dynamic limits so it has been improved on quite a bit. There was a good Channel 9 video on msdn that covered this but a las I cannot find it, however this article also talks about it

technet.microsoft.com/.../2007.03.vistakernel.aspx

re: The Case in the Corner Series: Session Pool Exhaustion

WayneM33 — Thu, 15 Jul 2010 22:41:09 GMT

@ Chris Knight - I dont recall which one it was, Pretty sure it was a "gaming" quality one but I dont remember the exact model or even the manufacturer

@Malum - Terminal Services for Administration was enabled which counts (I believe the default sessionpoolsize defaults to a higher amount when TS is enabled in Application mode but I would have to test to be sure)

re: The Case in the Corner Series: Session Pool Exhaustion

Malum — Wed, 30 Jun 2010 03:52:14 GMT

Was Terminal Services actually enabled? Is the SessionPoolSize bigger by default on Windows editions that actually support Terminal Services?

re: The Case in the Corner Series: Session Pool Exhaustion

Tobias Redelberger [MVP - SBS] — Sun, 27 Jun 2010 10:28:30 GMT

I like the background information which deliver deep insight one can use for future or similar support cases. Good Job!

re: The Case in the Corner Series: Session Pool Exhaustion

Chris Knight — Tue, 22 Jun 2010 16:11:18 GMT

Out of interest do you know what display adapter driver was being used? I've come across this problem before on Windows XP and Windows Server 2003 where the graphics driver was being sloppy in its memory allocations. Reverting to the VGA driver was an acceptable workaround. Although it really is still poor design that a session can be DoS'ed by GDI/USER object starvation. If the developers insist on leaving these resource bottlenecks for the sake of compatability, then a watchdog process should be introduced to trigger eventlog entries with meaningful remediation steps. Pulling out a kernel debugger for this type of stuff just highlights the massive fail in systems design and O+M process development within Microsoft.