I hope so. Most of the times, the unmanaged resources would not get disposed
and still hang in there, if you're using .NET 1.0, you have another headache
too. If your object becomes big enough (more than 85000 bytes) then it
automatically goes into generation 2 level object (occupying large object
heap, which is at a far* location), so GC will never touch it until it sees
there are no more Generation 0 and 1 items in its list to knock down. That
would be long enough to choke a system. Luckily MS fixed that issue in 1.1.
My principle is if you are not using it, dispose/close it.
"NeedHelp" wrote:
You know what we didnt close it. You think that would be the problem but the
problem won't happen for a good 20 hours or so or until peak times during the
day, do you still think it is the closing of the xmltextreader?
"Rama.NET" wrote:
Did you close your XmlTextReader object?
"NeedHelp" wrote:
Our ASP.NET application receives around 90 anonymous hits/sec while Requests
Executing usually stays around 15-25. This is good and our server performs
well
What our app does is load a remote XML URL with xmltextreader and
xmldocument load then transcribes the XML through a stylesheet and displays
it as a webpage.
The Problem is sometimes the Requests Executing will shoot up to 125-150 and
all of a sudden we'll get a server too busy error. I don't understand why
this is happening? I tried putting this in my web.config file:
<httpRuntime executionTimeout="6"/>
But still the requests executing will jump to 125-150 and stay like that but
the anonymous rec/sec stays the same, this is driving me crazy!
Does anyone know why this is happening?
Thanks
