Re: Timeout for RPC call via TCP/IP
From: Arkady Frenkel (arkadyf_at_hotmailxdotx.com)
Date: 07/27/04
- Next message: Arkady Frenkel: "Re: Using Win32_NetworkAdapterConfiguration to change IP doesn't w"
- Previous message: Arkady Frenkel: "Re: Locking a file over a network"
- In reply to: Thore Karlsen [MVP DX]: "Re: Timeout for RPC call via TCP/IP"
- Next in thread: Arkady Frenkel: "Re: Timeout for RPC call via TCP/IP"
- Reply: Arkady Frenkel: "Re: Timeout for RPC call via TCP/IP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Jul 2004 14:44:34 +0300
20c is default time for service to start , no connection to TCP/IP
Arkady
"Thore Karlsen [MVP DX]" <sid@6581.com> wrote in message
news:jgm2g05vdoohe797mk860p5mr8njk8tn4a@4ax.com...
> On Fri, 23 Jul 2004 09:07:23 +0200, "Frank Franzoni"
> <franzoni@gepasoft.de> wrote:
>
> >> Try RpcBindingSetOption with RPC_C_OPT_CALL_TIMEOUT. I've only tested
it
> >> briefly, but it seems to work. (Only on XP, though.)
>
> >Thanks for your quick answer.
> >I tried this option but it is behaving strangly. For the first rpc call
it
> >still takes 20 seconds until the call is
> >returned with an error.
> >When the network is interrupted after the first successful rpc call, all
> >following calls are returned within the time set in the option.
> >I suspect that this 20 seconds timeout does not come from the rpc runtime
> >but from tcp/ip.
> >Do you have an idea where to shorten this 20 seconds?
>
> It looks like the first RPC call is treated specially, and perhaps the
> alternative code path doesn't respect the timeout. I tried looking at
> the source code for the RPC implementation to see what was going on, but
> it's too complex to get an overview quickly.
>
> I'm not sure if there's a fix for this problem. I've searched for this
> kind of information before (timeouts, call cancellation, asynchronous
> calls), and there's precious little information about it apart from
> MSDN. I get the impression very few people are using these facilities.
> Or if they are, they must not be needing/seeking help online.
>
> The lack of control you have over what's going on behind the scenes with
> RPC is very frustrating, and if you expect to use it over faulty/slow
> connections I would recommend (based on my experiences) that you at
> least consider alternatives. Building a robust, responsive, and fault
> tolerant application around RPC is extremely hard.
>
> --
> Be seeing you.
- Next message: Arkady Frenkel: "Re: Using Win32_NetworkAdapterConfiguration to change IP doesn't w"
- Previous message: Arkady Frenkel: "Re: Locking a file over a network"
- In reply to: Thore Karlsen [MVP DX]: "Re: Timeout for RPC call via TCP/IP"
- Next in thread: Arkady Frenkel: "Re: Timeout for RPC call via TCP/IP"
- Reply: Arkady Frenkel: "Re: Timeout for RPC call via TCP/IP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
