Yea, we do get deadlock errors every now and again. My biggest problem is
that everything runs "In-Process" with the ASPNET Worker process, so I can
not see which assembly is the one that is causing the problems. Is there any
way that we can check that type of theng? What do you suggest?
"Ken Schaefer" wrote:
> Anything in the Windows Event Logs? Deadlocks for example?
>
> Cheers
> Ken
>
>
> "W1ld0ne74" <W1ld0ne74 RemoveThis @hotmail.com> wrote in message
> news:B24910C2-DC28-4E74-8B02-5B140250DB53@microsoft.com...
> > Can anyone shed some light on why my ASPNET_WP keep recycling. I'm
> > guessing
> > it's the we app that is running, but how do you go about fault finding
> > something like that?
> >
> > It's mostly .Net so all the assemblies run in a single aspnet_wp. This
> > component builds up memmory and processor recourses until it dies or gets
> > the
> > server gets restarted (Which at the moment needs to happen up to 8 times
> > per
> > day)
> >
> > Any help would be much apreciated.
> >
> > Thanks
> > David Taylor
>
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: ASP.Net Worker Process Recycling allot