J
Jarrod Hermer
Hi All,
I am trying to debug a strange problem of duplicate entries in my
database when I came across the following errors in the event log (see
bottom of mail). The web server runs the database as well but it is not
hit very hard, I would say there are about 20 request/sec constantly
thought the day. The only potentially suspect app is a Linux based
program that makes requests to IIS. Other than that I cannot think of
any reason why the asp.net worker thread should be restarting of worse
deadlocking.
I have read KB articles 321792, 329956 and 325947. They however only
seem to refer to .NET 1.0. Where all our apps are .NET 1.1.
Any ideas?
---------- Entries from Application Event Log --------------------------
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1003
Date: 2003/12/24
Time: 07:38:08
User: N/A
Computer: MYBEAT-SERVER
Description:
aspnet_wp.exe (PID: 7172) was recycled because it was suspected to be
in a deadlocked state. It did not send any responses for pending
requests in the last 180 seconds. This timeout may be adjusted using the
<processModel responseDeadlockInterval> setting in machine.config.
Plus a whole lot of these, about one every TWO hours!
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1000
Date: 2003/12/23
Time: 05:54:43
User: N/A
Computer: MYBEAT-SERVER
Description:
aspnet_wp.exe (PID: 11060) stopped unexpectedly.
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1000
Date: 2003/12/23
Time: 03:07:42
User: N/A
Computer: MYBEAT-SERVER
Description:
aspnet_wp.exe (PID: 10860) stopped unexpectedly.
I am trying to debug a strange problem of duplicate entries in my
database when I came across the following errors in the event log (see
bottom of mail). The web server runs the database as well but it is not
hit very hard, I would say there are about 20 request/sec constantly
thought the day. The only potentially suspect app is a Linux based
program that makes requests to IIS. Other than that I cannot think of
any reason why the asp.net worker thread should be restarting of worse
deadlocking.
I have read KB articles 321792, 329956 and 325947. They however only
seem to refer to .NET 1.0. Where all our apps are .NET 1.1.
Any ideas?
---------- Entries from Application Event Log --------------------------
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1003
Date: 2003/12/24
Time: 07:38:08
User: N/A
Computer: MYBEAT-SERVER
Description:
aspnet_wp.exe (PID: 7172) was recycled because it was suspected to be
in a deadlocked state. It did not send any responses for pending
requests in the last 180 seconds. This timeout may be adjusted using the
<processModel responseDeadlockInterval> setting in machine.config.
Plus a whole lot of these, about one every TWO hours!
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1000
Date: 2003/12/23
Time: 05:54:43
User: N/A
Computer: MYBEAT-SERVER
Description:
aspnet_wp.exe (PID: 11060) stopped unexpectedly.
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1000
Date: 2003/12/23
Time: 03:07:42
User: N/A
Computer: MYBEAT-SERVER
Description:
aspnet_wp.exe (PID: 10860) stopped unexpectedly.