"Goran Sliskovic" <gsliskov@yahoo.com> wrote in message
news:OioNwgkZHHA.2320@TK2MSFTNGP03.phx.gbl...
>
> "Howard Swope" <hswopeATtrafficDOTcom> wrote in message
> news:u9HFDCkZHHA.3520@TK2MSFTNGP04.phx.gbl...
>> I have a thread that is making a remoting call. Another thread calls to
>> abort this thread, which is supposed to fire a ThreadAbortException on
>> the
>> thread that is making the remoting call. This does not happen.
>>
>> Any thoughts?
> ...
>
> Threads can be aborted only in certain states and at certain moments. If
> thread is blocked in API call for example, it cannot be aborted by .NET
> framework. You may resort to aborting through native windows API, however
> this may lead to nasty consequences (if possible at all). I thnik that
> there
> should be some resources on the internet about .NET aborting calls.
>
> I also noticed that remoting threads cannot be aborted. Since it rarly
> happens, I leave them hanging. However, you must ensure that you don't
> hold
> any locks in the process...
>
> Regards,
> Goran
>
>

"Howard Swope" <hswopeATtrafficDOTcom> wrote in message
news:u9HFDCkZHHA.3520@TK2MSFTNGP04.phx.gbl...
> I have a thread that is making a remoting call. Another thread calls to
> abort this thread, which is supposed to fire a ThreadAbortException on the
> thread that is making the remoting call. This does not happen.
>
> Any thoughts?

Howard Swope wrote:
> Thanks for your response...
>
> The way that I have gotten around this is just making the calls from an
> AsyncDelegate and waiting for the return. This way the call is going out on
> a threadpool thread and the thread that I want to abort is waiting for it to
> return and it will throw the ThreadAbortException (I do cleanup in my
> finally block).