|
-
Jan 16th, 2002, 05:23 AM
#1
Thread Starter
New Member
MTS vs COM+
Sorry bu I posted this to the general forum aswell. Suspect it is better here..
Sorry if this is a long one!
I have a query regarding the behaviour of "Garbage Collection" in COM+. Any tips or advice would be gratefully received!
Current system: MTS on Win NT4
Porting to: Win2000 presumably with Com+?
Our system uses a persistent object hosted in MTS to receive messages from MSMQ. We start it via an executable that instantiates a COM object (ActX DLL) hosted in MTS and calls a "Start" method. Inside the COM object, the SafeRef instruction is issued to increase the reference count by one. The client exe then sets its object reference to nothing and then terminates. This leaves 1 instance of our COM object freewheeling in MTS receiving event notification from MSMQ. It sounds a bit wierd but it works a treat in the NT4/MTS
The trouble is, I have read that in Win2000, COM+ includes a "Garbage collection" utility that roots out COM servers with no client references and shuts them down. Would our current arrangement be rendered useless therefore? Can anyone tell me whether this is true or not and if Garbage collection can be turned off on a package basis?
If anyone has any ideas or indeed what might be a better approach then I would be grateful to hear any suggestions
Thanks in anticipation
from Jason
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|