if it is a web app, it is probably recycling in which case all running
threads are forcibly aborted. Check the event logs to see what they say
around that time of day or for anything strange

Signature
Regards,
Alvin Bruney - ASP.NET MVP
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc
> We have a thread running in our application, it runs a while loop that
> does
[quoted text clipped - 5 lines]
> to
> what could be causing this?
Jeremy Chapman - 27 Apr 2005 18:00 GMT
It is a windows forms application. It seems that every time the
Thread.Sleep hangs is about 2 or 3 minutes after Logical Disk Manager
Administrative Service stops. (This is a windows server 2003 machine and we
never had this problem on a windows 2000 server machine). If this is caused
by the Logical Disk Manager Administrative Service stopping, we don't know
why its stopping or what a work around would be.
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 4/27/2005
Time: 2:03:22 AM
User: N/A
Computer: DC1SERV64
Description:
The Logical Disk Manager Administrative Service service entered the stopped
state
> if it is a web app, it is probably recycling in which case all running
> threads are forcibly aborted. Check the event logs to see what they say
[quoted text clipped - 9 lines]
> > to
> > what could be causing this?
Willy Denoyette [MVP] - 02 May 2005 19:23 GMT
> It is a windows forms application. It seems that every time the
> Thread.Sleep hangs is about 2 or 3 minutes after Logical Disk Manager
[quoted text clipped - 27 lines]
> stopped
> state
This service isn't suposed to run in the first place (unless you run the
LDM), do you have any USB drives that might get connected/disconnected?
Willy.
Jeremy Chapman - 03 May 2005 20:03 GMT
Apparently this service is required because the server is connected to a
SAN. Looking at the service manager, the service is set to startup type
automatic and status is started.
> > It is a windows forms application. It seems that every time the
> > Thread.Sleep hangs is about 2 or 3 minutes after Logical Disk Manager
[quoted text clipped - 32 lines]
>
> Willy.
Willy Denoyette [MVP] - 03 May 2005 22:00 GMT
Hmmm, the "Logical Disk Manager" is always running, but not the "Logical
Disk Manager Administrative Service", the latter runs under control of the
former.
Willy.
> Apparently this service is required because the server is connected to a
> SAN. Looking at the service manager, the service is set to startup type
[quoted text clipped - 37 lines]
>>
>> Willy.