I am having a problem with one of my COM objects that gets instantiated in
session scope in an ASP page. This COM object is marked Threading Model =
both. This object makes calls on an out-of-proc server, WMI in this case,
and this object also has a sink interface implemented that WMI calls back on
to keep it informed of WMI events. When I test this component using my VB
test app everything works fine. When I test it via the ASP web page things
start to go wrong. I noticed that if I make a WMI call that causes events to
be fired back to me then the component will freeze on the call to the WMI
method for approx. three minutes, sometimes more depending on the method I
call, and then it returns and I get notified of the events via my sink
interface. Its an understatement to say that a three minute wait is
unacceptable. Does IIS do something to prevent me from receiving callbacks?

As you can guess there are many more details that I could add to this
e-mail, but I wanted to keep this message as concise as possible. If you
have any ideas, but need more information feel free to ask me. I have looked
into this problem quite extensively so I should be able to easily give you
the details you need.

John Bigley

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]