App Pool Lock
am 28.06.2007 17:45:22 von Kevin Antel
We have an applicatoin on .NET 1.1.4322 with Windows 2003 Server SP1. For
some time, it's plagued us that this one applciation keeps locking. It can
take 1 - 2 months of straight use, (without a server reboot) but it
eventually locks hard. I can shut down the web and hit the page to get a
site error message, start the web, and it still results in a standard IE
error message. I have to recycle the app pool to get it to work. This is
the only web on this app pool, so no other sites are effected. However,
it's happened several times now.
The app pool is set to recycle ever night at 3:00 a.m. and after being idle
for 20 minutes.
2 questions, any ideas what might be causing these hard locks and two, any
idea on how to troubleshoot it?
Thanks.
Re: App Pool Lock
am 01.07.2007 11:44:25 von David Wang
On Jun 28, 8:45 am, "Kevin A" wrote:
> We have an applicatoin on .NET 1.1.4322 with Windows 2003 Server SP1. For
> some time, it's plagued us that this one applciation keeps locking. It can
> take 1 - 2 months of straight use, (without a server reboot) but it
> eventually locks hard. I can shut down the web and hit the page to get a
> site error message, start the web, and it still results in a standard IE
> error message. I have to recycle the app pool to get it to work. This is
> the only web on this app pool, so no other sites are effected. However,
> it's happened several times now.
>
> The app pool is set to recycle ever night at 3:00 a.m. and after being idle
> for 20 minutes.
>
> 2 questions, any ideas what might be causing these hard locks and two, any
> idea on how to troubleshoot it?
>
> Thanks.
You can use a tool like DebugDiag to take a stack backtrace of all the
threads in the process when it appears to be completely "locked" to
see what they are locked on, and hopefully that gives you better
clues.
For example, maybe your application may have a logical failure which
mishandles a lock to a certain resource under error handling
conditions, which then causes subsequent access to that resource to be
tied behind the lock. Why it happens -- it completely depends on the
application's source code itself, which is arbitrary.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//