COM+ Pooled Components not deactivated on Windows 2003

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dany - 30 Mar 2006 18:25 GMT

I'm having problems with a COM+ Server Application written in C# .net 1.1. The Problem only occurs on Windows 2003.
I have implemented a COM+ Application containing a pooled COM+ Component. After accessing the COM+ Component using a ProgID the component isn't deactivated and stays in activated (=referenced) and not released to the pool. This happens when accessing from a ASP.net application or even a VBScript:

set umbObj = CreateObject( "UmbrellaNT.K2Quality.UmbrellaNT" )
set umbObj = Nothing

Even after the calling ASP.net or VBScript application closes the COM+ Component stays activated. As I mentioned on Windows XP this Problem does not occur.

Does anyone have an idea or are any similar Problems in Windows 2003 known?

Thanks for any help.
Dany

Reply to this Message

VB6 To .NET - 30 Mar 2006 18:42 GMT

Maybe implement IDisposable and the dispose pattern in your .NET assembly so
your resources are cleaned up properly.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/c
pconFinalizeDispose.asp

> I'm having problems with a COM+ Server Application written in C# .net 1.1.
> The Problem only occurs on Windows 2003.
[quoted text clipped - 16 lines]
> Thanks for any help.
> Dany

Reply to this Message

Rate this thread:

COM+ Pooled Components not deactivated on Windows 2003

Free Magazines