Wei-Dong XU,
Thank you very much for looking after this thread.
Yes, I did read several times this interesting article:
http://support.microsoft.com/?id=169321
This is the reason I was examining the window station. I added some code
to the DCOM to log in a text file the name of the window station used by
the DCOM when it initialised, using the GetProcessWindowStation API. I
did the same for the ISAPI DLL.
The logs indicate that the ISAPI is initialised only once with one
window station while the DCOM is initialised several time with different
window station names. The DCOM appears several times in memory but we
currently only use one set of credential.
I observed that all the threads inside a DCOM instances are all created
within 25 minutes of the instance initialisation. I have never observed
threads created after 25mn of the DCOM instance its belong. But I am not
looking at it all the time!
If the credential does not change, the calling process (ISAPI DLL) stay
the same (same window station and same SID) why does the DCOM is
initialised several times from time to time in different window stations
and at other time just a new module (thread) is created in exiting DCOM
instance?
The question seems to be related to window station. Why do Windows or
IIS 6 decide to create a different window station from time to time even
if nothing changed?
*** Sent via Developersdex
http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
>> Stay informed about: IIS 6 and DCOM instanciation