"Mrinal Kamboj" wrote:

> Hi Rahul ,
>
> Following are my views regarding the issue that you are facing :
>
> 1. When you say one of the thread , can you just switch on some tracing
> and check the thread Id , just to ensure that it arbitrary happens with
> any thread or the same thread creates an issue , which is actually quite
> unlikely , but you can use Appdomain class for this purpose .
>
> 2. Whether it's managed / unmanaged code ultimately all the API's that
> do the thread creation under the cover access win 32 code , as threads
> are exclusively OS privileges and believe me if at any point of time
> depending upon the scehduling dynamics MS also warns about some such
> issues in case of multithreaded Apps .
>
> 3. Actually in managed code when ever thread abortion takes place then
> it's bound to throw the ThreadAbortException , but in you case since
> it's not happening , only reason i can think of is , threading
> implemented in un managed code and it is calling a managed method , so
> each executing worker thread has a call to the method and exception at
> point on call stack doesn't ensures going to your method's finally block
> , otherwise exception with in the method can't miss it .
>
> I think you can try :
>
> Increasing some more sleep time / thread , to see if issue gets resolved .
>
> Ensure that every thread created is of normal priority there's no high
> priority thread , but starving others , which can done in unmanaged code .
>
> Hope this somewhat helps ,
>
> Mrinal
>
>
>
> Rahul Anand wrote:
>
> > I have a problem in my multithreaded application. The problem is reproducible
> > very rarely, only once in 6000 similar execution (through same code path).
> >
> > Problem: One of multiple threads gets abnormally terminated. It does not go
> > through the try-catch-finally sequence. The mehtod gets hanged and the object
> > used inside the method gets collected by GC.
> >
> > Background about the Application: I am using COM-Interop. The threads are
> > created in unmanaged code which calls methods from managed code. One of the
> > thread abnormally terminates when executing .NET method.
> >
> > Observation: I have observed that the thread terminates only in those
> > methods where I am using IO Stream operation.
> >
> > As I said this is very rare and the same code works fine except once or
> > twice in 6000 executions.
> >
> > This is the code under which thread terminates mostly.
> >
> > <CODE>
> >
> > // I am generating log file for comments, to see the actual execution path
> > public string GetRequestFile(string strFileName)
> > {
> > // Log method enterd
> > StreamReader reader = null;
> > try
> > {
> > reader = new StreamReader(strFileName);
> > return reader.ReadToEnd();
> > }
> > catch(Exception exc)
> > {
> > // Log error occurred
> > throw;
> > }
> > finally
> > {
> > if(reader != null)
> > reader.Close();
> > // Log finally executed
> > }
> > }
> >
> > <CODE>
> >
> > Please let me know if there is any similar bug reported under .NET I/O
> > Stream operation.
> >
> > Does CLR forcefully terminates a thread in a way that it bypasses the
> > finally block?
> >
> > Thanks in advance for your help.
> >
> > Cheers,
> > Rahul Anand