Critical: Asp.Net web app stalling

Critical: Asp.Net web app stalling

am 10.09.2007 16:21:50 von Tom wilson

We've been running an ASP.Net app for quite some time now. Suddenly,
the app is locking up for no apparent reason.

The app starts with a login screen that asks for a code. The code is
entered, looked up in a SQL 2000 database and redirected to the main
page.

We've stepped through this code. The database is opened, the code
verified, certain data is loaded into session memory and a
response.redirect is made to the main page except it never gets there.
It just hangs on the redirect. This doeesn't happen all the time.
Older codes don't cause this problem it seems. It's not a database
problem, the code opens the database and gets the info it needs but
the redirect hangs. This happens on any server we try to run it on.

On the production server, the app has its own application pool. On 2
development servers is shares the same app pool and has the same
problem. These events appear in the event logs of the server(s):

Event ID: 1073

Failed to process request.

Exception: System.AppDomainUnloadedException
Message: Attempted to access an unloaded AppDomain.

Event ID 1073:

Failed to process request.

Exception: System.Threading.ThreadAbortException
Message: Thread was being aborted.

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 9/10/2007 8:23:16 AM
Event time (UTC): 9/10/2007 12:23:16 PM
Event ID: 0176352ab3cf4e0c8dce92402b2b4b1a
Event sequence: 79
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1921793534/Root-1-128338986334184959
Trust level: Full
Application Virtual Path: /
Application Path: c:\inetpub\wwwroot\challenge\
Machine name: WWW1

Process information:
Process ID: 3344
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: ThreadAbortException
Exception message: Thread was being aborted.

Request information:
Request URL: http://www.mysite.com/Main/RegisterTeam.aspx
Request path: /Main/RegisterTeam.aspx
User host address: xxx.xxx.xxx.xxx
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Event ID: 1013:

A process serving application pool 'ChallengePool' exceeded time
limits during shut down. The process id was '532'.

-----------------

All I can see is that these are telling me the requests for the above
page failed but no indication as to why. This happens on 3 different
servers. Each time, the CPU usage goes through the roof.

All are W2003 R2 servers running IIS 6.

Any ideas? I have no idea where to even start. Any help would be
appreciated, thanks!

Re: Critical: Asp.Net web app stalling

am 10.09.2007 16:39:48 von Tom wilson

Nevermind, a randomizer in the code was in and endless loop,
generating the same codes over and over again.

Thanks anyways...



On Mon, 10 Sep 2007 10:21:50 -0400, Tom wilson
wrote:

>We've been running an ASP.Net app for quite some time now. Suddenly,
>the app is locking up for no apparent reason.
>
>The app starts with a login screen that asks for a code. The code is
>entered, looked up in a SQL 2000 database and redirected to the main
>page.
>
>We've stepped through this code. The database is opened, the code
>verified, certain data is loaded into session memory and a
>response.redirect is made to the main page except it never gets there.
>It just hangs on the redirect. This doeesn't happen all the time.
>Older codes don't cause this problem it seems. It's not a database
>problem, the code opens the database and gets the info it needs but
>the redirect hangs. This happens on any server we try to run it on.
>
>On the production server, the app has its own application pool. On 2
>development servers is shares the same app pool and has the same
>problem. These events appear in the event logs of the server(s):
>
>Event ID: 1073
>
>Failed to process request.
>
>Exception: System.AppDomainUnloadedException
>Message: Attempted to access an unloaded AppDomain.
>
>Event ID 1073:
>
>Failed to process request.
>
>Exception: System.Threading.ThreadAbortException
>Message: Thread was being aborted.
>
>Event code: 3005
>Event message: An unhandled exception has occurred.
>Event time: 9/10/2007 8:23:16 AM
>Event time (UTC): 9/10/2007 12:23:16 PM
>Event ID: 0176352ab3cf4e0c8dce92402b2b4b1a
>Event sequence: 79
>Event occurrence: 1
>Event detail code: 0
>
>Application information:
> Application domain: /LM/W3SVC/1921793534/Root-1-128338986334184959
> Trust level: Full
> Application Virtual Path: /
> Application Path: c:\inetpub\wwwroot\challenge\
> Machine name: WWW1
>
>Process information:
> Process ID: 3344
> Process name: w3wp.exe
> Account name: NT AUTHORITY\NETWORK SERVICE
>
>Exception information:
> Exception type: ThreadAbortException
> Exception message: Thread was being aborted.
>
>Request information:
> Request URL: http://www.mysite.com/Main/RegisterTeam.aspx
> Request path: /Main/RegisterTeam.aspx
> User host address: xxx.xxx.xxx.xxx
> User:
> Is authenticated: False
> Authentication Type:
> Thread account name: NT AUTHORITY\NETWORK SERVICE
>
>Event ID: 1013:
>
>A process serving application pool 'ChallengePool' exceeded time
>limits during shut down. The process id was '532'.
>
>-----------------
>
>All I can see is that these are telling me the requests for the above
>page failed but no indication as to why. This happens on 3 different
>servers. Each time, the CPU usage goes through the roof.
>
>All are W2003 R2 servers running IIS 6.
>
>Any ideas? I have no idea where to even start. Any help would be
>appreciated, thanks!