Deadlock

From: Venkat <Venkat@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 9 Jun 2005 22:09:03 -0700

Hi,
We have a dozens of VB6 components, developed some 5 years before, we
have now few .Net components which references these files. Ideally we are
using Biztalk server and referencing these VB6 components into that, what
happens is that during actual transaction with several instances, the
process(biztalk)
gets automatically shutdown.

on researching the problem it was found that all VB6 compentes were STA and
so when loaded into memory it caused a deadlock problem. The solun ideally is
to convert all the vb6 componets to .net components, but as of now this is
practically impossible.

can any one suggests an alternate method so that the process goes with MTA
instead of STA or atleast any ways to minimise the deadlock condition?
.

Follow-Ups:
- Re: Deadlock
  - From: Valery Pryamikov

Prev by Date: RE: biztalk server hostname change
Next by Date: Pipeline Components play nice ?
Previous by thread: biztalk server hostname change
Next by thread: Re: Deadlock
Index(es):
- Date
- Thread

Relevant Pages

Re: Deadlock
... > believe that about 80% of legacy VB6 components are used in the way that is ... >> have now few .Net components which references these files. ... >> on researching the problem it was found that all VB6 compentes were STA ... >> so when loaded into memory it caused a deadlock problem. ...
(microsoft.public.biztalk.general)
Com to .Net
... We have a dozens of VB6 components, developed some 5 years before, we ... have now few .Net components which references these files. ... so when loaded into memory it caused a deadlock problem. ...
(microsoft.public.dotnet.general)
Re: Deadlock
... I believe that about 80% of legacy VB6 components are used in the way that is safe for marking them multithreaded (i.e.. ... We have a dozens of VB6 components, developed some 5 years before, we have now few .Net components which references these files. ... so when loaded into memory it caused a deadlock problem. ... instead of STA or atleast any ways to minimise the deadlock condition? ...
(microsoft.public.biztalk.general)
STA and MTA
... We have a dozens of VB6 components, developed some 5 years before, we ... have now few .Net components which references these files. ... so when loaded into memory it caused a deadlock problem. ...
(microsoft.public.dotnet.languages.csharp)
Re: STA and MTA
... > have now few .Net components which references these files. ... > using Biztalk server and referencing these VB6 components into that, ... > on researching the problem it was found that all VB6 compentes were STA ...
(microsoft.public.dotnet.languages.csharp)