Passing "dead" callbacks via DCOM, and timeouts

I'm using VB6 and NT4 SP3 and DCOM.
I have a single threaded server assigning jobs to a multi-threaded worker. The server passes callbacks to the worker. If this owner of this callback object (a client on another machine, passed via DCOM to the server) has been terminated then the server waits 100 seconds whilst trying to pass the callback to the worker, and then times out.

Is it possible to check if the callback is valid, instead of having to wait for 100 seconds for the timeout? Or is it possible to change this timeout value to something smaller?

Thanks in advance,
Fred Forsyth, Software Engineer.
fredforsythAsked:
Who is Participating?
 
covingtonConnect With a Mentor Commented:
Try setting App.OleServerBusyTimeout to a value of 1000. The published default (in help) is 10,000, but I think it's really 100,000.

0
 
fredforsythAuthor Commented:
I tried the above and it did indeed reduce the wait from 100 seconds, but I couldn't get it to go below 35 seconds. If this is a problem with the OS then I will accept your answer, but is it possible to get a smaller wait?
0
 
covingtonCommented:
I haved used this to reduce the timeout below 30 seconds. The important thing to remember is that the delay applies from the time that the client recognizes that the server is busy, not from the inital time that the call is made. Does this make sense?

Other than that cryptic piece of information, I'm afraid that I don't have much more to offer.


0
 
fredforsythAuthor Commented:
Thanks for the help.
Fred.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.