Re: ASP stops responding

From: mjkahn (mjkahn_at_discussions.microsoft.com)
Date: 03/27/05 

Date: Sun, 27 Mar 2005 09:01:02 -0800

"Bob Barrows [MVP]" wrote:

> You're describing one of the principle symptoms that people encounter when
> they store apartment-threaded objects in session or application. I do not
> understand why you are dismissing this as a possible cause out-of-hand.

Now that I think about it (some more), *why* is this a symptom that people
encounter when storing apartment-threaded objects in session or application
variables? I asked about storing objects in session variables in another
thread, and I think there was a consensus that the principal concerns are
memory and performance, but not hangs. (Yeah, I suppose a hang is the
ultimate performance issue, but in my reading, I haven't seen references to
hangs around this practice.)

Is the concern that, because these objects can only run in the threads that
created them, some kind of threading deadlock might occur? If so, could
someone please describe that scenario? I'd really like to understand what's
going on, both out of general curiosity and also so I can have some
confidence that any actions I take are really addressing the underlying
problem.

Thanks very much,

MJ.