The
defaultServiceTimeout build descriptor
option specifies the maximum valid number of milliseconds that elapse
between two events:
- In the case of a Rich UI application, the events are when the
EGL Rich UI proxy (on the application server) invokes a web service
and when the proxy receives a response
- In the case of an EGL-generated Java™ requester,
the events are when the EGL Runtime invokes a web service and when
that code receives a response
If the response takes longer than the specified maximum, the EGL
Runtime throws a ServiceInvocationException.
Setting a timeout is partly a matter of trial and error:
- Take into account a variety of factors, such as local network
traffic, internet traffic, and server response time. Those factors
mean that two invocations of the same service are likely to take a
different amount of time under different conditions.
- Consider the nature of your application. If your code is waiting
for a credit approval, you might set a high timeout value to avoid
charging the user twice. If your code is making a bid in an online
auction bid, you might set a low timeout value so that the user can
make an additional bid quickly.
- Use timeout values that vary from one another by one or more seconds.
The option defaultServiceTimeout is available
for Rich UI and EGL-generated Java.
For Rich UI, you can override the value by setting the timeout property
on the call statement that invokes the service.
The default is an infinite wait. (In EGL version 7.5.1, the default
was 10,000).
Compatibility
Table 1. Compatibility considerations
for defaultServiceTimeout| Platform |
Issue |
| COBOL generation |
The build descriptor option has no effect. |
| Rich UI |
The build descriptor option has no effect during
access of a dedicated service. |