Many TCP Connections Are Established for COM+ Proxy/Stub

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

I have a problem where many TCP connections are being established when
making Distributed Component Object Model (DCOM) calls to a COM+
server application.

The COM+ component is written in VB6. The client which is making the
COM+ calls is an ASP page running within IIS5.

KB301512 describes the symptoms of my problem, but I don't think that
dynamic cloaking is in place. I determined this by calling
GetUserName() - which returned the user that the COM+ component was
configured to run as and not the user accessing IIS via integrated
security.

When the COM+ component shuts down the ports are closed down also. So
I've set the minutes idle until shutdown to 1 minute, but on busy days
the webserver is not idle for a whole minute throughout the working
day!

We're investigating the use of RpcMgmtEnableIdleCleanup() but as the
client is stateless and multithreaded (ASP Page) it is not obvious
how to implement it.

What we're doing is very common (having a 2-tier webserver using COM+
and IIS5) so I'm suprised that this hasn't been documented on msdn
before - Do knowledgebase articles get purged to make room for the new
techonolgies (dot net and 2k3 Svr etc.)?

Any help on this would be most welcome.

Kind regards,

Antony Briggs

.