VB Out of Process Component not accessible sometimes

[AC123]

I have a DCOM application which has an out of process component. I have configured it on a remote server using
DCOMCNFG utiliy. I also have it running.
(By just double clicking the .exe file)

The problem is that sometimes it's not accessible from the client applications? Is there any fact that if the component is not used by any client for a long time
it just dies?

Any advise please...

 

[Yazster]

Hi AC123,

Please see ``DCOM SERVER HANGING`` thread. Seems to be related....

Yazster

 

[SemperFiDownUnda]

components normally realease themselves from memory after the last client releases them. You can set components to retain in memory if you want. But I'm not sure if this is your exact problem because just because a component drops from memory doesn't mean that the host application drops. Retain in memory is there more to speed up execution on infrequently used components by stopping the need for full initialisation every time the component called.