Under certain conditions, a class that is derived from the System.EnterpriseServices.ServicedComponent
class that runs in a COM+ application may stop responding
This problem is caused by an Activity deadlock. Activities
can deadlock on multithreaded applications because of an asynchronous cleanup
of component references.
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
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
FIX: Various problems when you call transactional COM+ components from ASP.NET
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
For more information about Enterprise Services
(COM+) in .NET, visit the following Microsoft Web site: