On this page:
Overview of Invocation Timeouts
Invocation timeouts let an application specify the maximum amount of time it's willing to wait for invocations to complete. If the timeout expires, the application receives
InvocationTimeoutException as the result of an invocation.
Use connection timeouts to detect network failures in a reasonable period of time.
Invocation timeouts were introduced in Ice 3.6. In earlier Ice versions, connection timeouts were also used as invocation timeouts.
Configuring the Default Invocation Timeout
Ice.Default.InvocationTimeout establishes the default timeout value for invocations. This property has a default value of
-1, which means invocations do not time out by default. If defined to
-2, invocation timeouts are disabled and the Ice run time behaves like Ice versions < 3.6: it uses connection timeouts (defined on the endpoints) to wait for the response of the invocation. This setting is provided only for backward compatibility and might be deprecated in a future Ice major release.
Consider this setting:
This configuration causes all invocations to time out if they do not complete within five seconds. Generally speaking however, it's unlikely that a single timeout value will be appropriate for all of the operations that an application invokes. It's more common for applications to configure invocation timeouts on a per-proxy basis, as we describe in the next section.
Configuring Invocation Timeouts for Proxies
You have a couple of options for configuring invocation timeouts at the proxy level:
- Use a proxy property
Assuming you've defined a configuration property containing a proxy that your application reads using
propertyToProxy, you can statically configure an invocation timeout as follows:
InvocationTimeout proxy property specifies the invocation timeout that will be used for all invocations made via the proxy returned by
To configure an invocation timeout at run time, use the
ice_invocationTimeout factory method to obtain a new proxy with the desired timeout:
Invocation Timeout Failures
An application that configures invocation timeouts must be prepared to catch
The effects of an invocation timeout are limited to the client; no indication is sent to the server, which may still be busy dispatching the request. The Ice run time in the client ignores a reply for this request if the server eventually sends one.
Ice does not perform automatic retries for invocation timeouts.