Select the product you need help with
BUG: Multithreaded applications can deadlock because of asynchronous cleanupArticle ID: 327443 - View products that this article applies to. This article was previously published under Q327443 SYMPTOMS Under certain conditions, a class that is derived from the System.EnterpriseServices.ServicedComponent class that runs in a COM+ application may stop responding
(deadlock). CAUSE This problem is caused by an Activity deadlock. Activities
can deadlock on multithreaded applications because of an asynchronous cleanup
of component references. RESOLUTIONTo
resolve this problem, the client of the COM+ objects should systematically call the Dispose method. This call enables deterministic cleanup of the COM+
objects. You must call the Dispose method when you have finished using ServicedComponent objects. STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. REFERENCES
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
318000
(http://support.microsoft.com/kb/318000/
)
FIX: Various problems when you call transactional COM+ components from ASP.NET
312118 For more information about Enterprise Services
(COM+) in .NET, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/312118/
)
The system memory usage and the handle counts increase more than you may expect when your application contains components that are derived from the System.EnterpriseServices.ServicedComponent class
http://msdn.microsoft.com/en-us/library/ms973847.aspx
(http://msdn.microsoft.com/en-us/library/ms973847.aspx)
Properties |
Back to the top
