The Question and Answer Board

[Bob Zumbrunnen]

That one was a matter of timing. I restarted IIS without rebooting the computer. You just happened to be using the site when it happened.

Specifically, I set the isolation level in IIS to High (even though I know I tried this before), which made IIS restart itself.

I also just tried something else.

Though we're not running out of memory, we do make very heavy use of Session Variables.

VERY heavy use. And it was suddenly bugging me that the contents of any message that ever gets previewed gets stored as a session variable and doesn't get cleared until you write another message.

So I just added some code to the back-end posting routines that destroy the message text session variable as soon as the message is posted.

I don't know if it'll help. But it did occur to me that keeping potentially tens of thousands of bytes *per session* around in session variables is really wasteful and might even cause some instability. There are 1500 sessions alive right now and this goes upwards of 10,000 sessions during market hours.

I'll check from home this evening to see if this "fix" screwed anything up.

If it ends up being the solution to the reliability problem, it actually wouldn't surprise me. But I'm not optimistic that it will be.

Susie, the above isn't directed at you. I'm sure you heard a "Whoosh" sound about a foot above your head when you were reading it. <g>

But there are those who will understand what I'm saying.