Re: Threadpool thread termination.
- From: "Richard Grimes" <richardg@xxxxxxxx>
- Date: Wed, 19 Oct 2005 15:40:53 +0100
objectref wrote:
> hi to all folks here,
>
> let's say that i am using a threadpool and somehow, some threads in
> it just stuck.
> (endless loop or something like that).
They're stuck. You had better write them so that they don't go into an
endless loop.
Officially a .NET thread is an abstract unit. In practice in .NET v 1.1
there is a one to one correspondence between .NET threads and OS
threads, and so conceivably you could use Win32 to terminate a thread
pool thread. However terminating a thread in Win32 is not a nice thing
to do because you'll lose data, and so it's best not to do that.
Basically there is no alternative other than making sure that the code
that you'll run on the thread pool thread does not go into an endless
loop. If it's code that yiu do not have access to the source then
metaphorically give them a kick up the arse.
Richard
--
http://www.grimes.demon.co.uk/workshops/fusionWS.htm
http://www.grimes.demon.co.uk/workshops/securityWS.htm
.
- References:
- Threadpool thread termination.
- From: objectref
- Threadpool thread termination.
- Prev by Date: MCP for .net 2.0
- Next by Date: Re: old topic: ordered name/value pair class?
- Previous by thread: Threadpool thread termination.
- Next by thread: Re: Threadpool thread termination.
- Index(es):
Relevant Pages
|
