If you have a clue of when it is going to happen, you can watch perf
counters, et al. This is ideal, but not as realistic as some other choices.
Checking for open connections, memory use (although the GC methodology may
give you a wrong impression if you do not know the theory) and other no nos
is a good idea, however, so PerfMon can definitely be your friend.
Setting tracing on and viewing the .axd file can give some hint of what is
happening. You may want to add some custom trace variables to the trace, to
get a better idea of what is going on. Tracing will add some load, but you
can turn it off when you find the problem.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"Patrick" <pa********@bluemail.ch> wrote in message
news:Oq**************@TK2MSFTNGP10.phx.gbl...
Hello
I have an asp.net Application that is running on a live system. The
problem I have is that it crashes sometimes, that means, the application is not
running anymore. I have to stop and start the application pool.
Is there a way to debug the application in that moment to see why it
hangs? Has someone an Idea how to find out what it could be?
Thanks
Patrick