Debugging live application

[Patrick]

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

[Cowboy \(Gregory A. Beamer\) [MVP]]

Re: Debugging live application

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" <patrick911@blu email.ch> wrote in message
news:Oq2WCQ5UEH A.2908@TK2MSFTN GP10.phx.gbl...[color=blue]
> Hello
>
> I have an asp.net Application that is running on a live system. The[/color]
problem[color=blue]
> 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[/color]
hangs?[color=blue]
> Has someone an Idea how to find out what it could be?
>
> Thanks
> Patrick
>
>[/color]

[Patrick]

Re: Debugging live application

Hi Gregory

Thanks for your reply, but I don't have any idea when it happens, even not
what it could be... cuz have not really special code in it... but who knows,
something it must be. Is there no way to see what the application pool is
doing?

Thanks


"Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld @comcast.netNoS pamM>
schrieb im Newsbeitrag news:%23SMaxK6U EHA.3988@tk2msf tngp13.phx.gbl. ..[color=blue]
> 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[/color]
choices.[color=blue]
> 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[/color]
nos[color=blue]
> 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,[/color]
to[color=blue]
> 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" <patrick911@blu email.ch> wrote in message
> news:Oq2WCQ5UEH A.2908@TK2MSFTN GP10.phx.gbl...[color=green]
> > Hello
> >
> > I have an asp.net Application that is running on a live system. The[/color]
> problem[color=green]
> > 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[/color]
> hangs?[color=green]
> > Has someone an Idea how to find out what it could be?
> >
> > Thanks
> > Patrick
> >
> >[/color]
>
>[/color]