How does the front side timeout work?
How does the front side timeout setting work for IBM WebSphere DataPower SOA Appliances?
Clarification on the use of the Front Side Timeout might be needed.
The definition of Front Side Timeout states:
"Controls the amount of time a front side client connection can be idle before being abandoned within a transaction. "
In this definition, the timer starts when a client connection goes from active to idle. Also, the timer does not count except when waiting on the client in context of an active client transaction.
For example, if the client has data to send and the connection stalls sending that data for greater than the configured timeout, the front side timeout should trigger.
If the client has not sent the entire request but is waiting to receive data (that is, the DataPower appliance wants to send the client data) and the connection stalls receiving that data for greater than the configured timeout, the front side timeout should trigger.
However, if the client sent the entire request, and is waiting for the DataPower appliance to send data from the backend, the client side timeout should not trigger.
More support for:
IBM DataPower Gateways
Software version: 4.0.1, 4.0.2, 5.0.0, 6.0.0
Operating system(s): Firmware
Software edition: Edition Independent
Reference #: 1613359
Modified date: 04 September 2013