RFC Call Timeout

Question

Hello,
Is there any possibility to configure a timeout for an RFC call using .NET Connector 3.0?
RfcDestination.Ping() throws an RfcCommunicationException in about 6..7 seconds if the backend system is not reachable:
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       timeout occured
TIME        Tue Apr 15 15:37:18 2014
RELEASE     720
COMPONENT   NI (network interface)
VERSION     40
RC          -5
MODULE      nibuf.cpp
LINE        4795
DETAIL      NiBufIConnect: route connect '/H/xxx.xxx.xxx.xxx/H/xxx.xxx.xxx.xxx'
            timeout
COUNTER     2
The same exception type thrown from the same RfcDestination.Ping() can originate from another cpp file:
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner 'xxx.xxx.xxx.xxx:xxxx' not reached
TIME        Fri Mar 21 15:01:36 2014
RELEASE     720
COMPONENT   NI (network interface)
VERSION     40
RC          -10
MODULE      nixxi.cpp
LINE        3285
DETAIL      NiPConnect2: xxx.xxx.xxx.xxx:xxxx
SYSTEM CALL connect
ERRNO       10060
ERRNO TEXT  WSAETIMEDOUT: Connection timed out
COUNTER     2
But in the latter case the timeout is much longer, about 30 seconds.
Is it possible to configure timeouts?

Answer 1

Hi Hynek,
I would like to make timeouts predictable. If I set the timeout to 10 seconds I would expect that the operation would succeed or fail not later than in 10 seconds.
Time decorator approach could be one possibility, thanks for the hint! Unfortunately, that one is not a panacea because using another thread for functional module call would not be always desirable.
Tweaking system settings would be the option I would try to avoid because of several reasons. E.g. because my process would not have full control over the settings and another process can easily change them. Or or because my process would not have enough permissions to change the settings. But thanks for that hint as well.
Regards,
Michail