Layer 7 API Management

Expand all | Collapse all

Route via HTTPS(s) Assertion : Read TImed Out

Jump to Best Answer
  • 1.  Route via HTTPS(s) Assertion : Read TImed Out

    Posted 11-05-2019 06:08 AM
    Hi Guys,

    I am using Route via HTTPS(s) assertion and configured Read Time Out : 15000 ms.
    But, when I check the Dashboard, some requests show Response Time BackEnd as more than 15000 ms.

    How is this possible ?


  • 2.  RE: Route via HTTPS(s) Assertion : Read TImed Out
    Best Answer

    Posted 11-05-2019 08:00 AM
    Our docs reference that the readtimeout may not be the complete response and may be longer transaction then the specified interval.

    Read Timeout
     defines the maximum time (in milliseconds) allowed for response data (not necessarily the complete response) to be read for the outbound request. If exceeded, the routing fails (or failover). To override the system default, clear the 
    Use System Default
    ] check box and enter a value. You may reference context variables.
    The system default for this timeout is defined by the 
    cluster property, which defaults to 60 seconds if the property is not explicitly set. 
    *** The Read Timeout is triggered each time there is communication from the backend server. As a result, it is possible that the actual communication time is much longer than the value set for "Read Timeout". ***
    The Read Timeout should not exceed the SLA that is defined for your service. If a SLA is not defined, one should be created and communicated to your clients. If the client is expecting a response from the Gateway within 2000ms, the Read Timeout should be approximately 1500ms. It should never be greater than the SLA for the service, otherwise the Gateway would potentially fail the SLA if or when the backend service is unavailable.

  • 3.  RE: Route via HTTPS(s) Assertion : Read TImed Out

    Posted 01-16-2020 07:18 AM

    The documentation article means that the response comes intermittently.
    What does this imply, that the target application is streaming the data back to CA API Gateway?

    How can I verify that the streaming is the sole reason and not any other reason is behind this behaviour ?

    Please explain.