Http call timeout

[cristianmusat]

Hi ,
I've try any combination of configuration but I can not setup a serviceProxy to use http call timeout. My case is very simple - to return and error if call to other service duration is more than X seconds.
This configuration that not work:

  <serviceProxy name="TestService" port="80">
        <path>/gateway/services/test</path>
        <wsdlRewriter />
        <wsdlPublisher wsdl="/opt/api-gateway/conf/wsdl/test/test.wsdl"/>
        <httpClient>
           <httpClientConfig maxRetries="1">
               <connection keepAliveTimeout="4000" timeout="5000"/> <!--- this does do nothing>
           </httpClientConfig>
        </httpClient>
        <target url="https://test-service.anydomain.local/webservice">
              <ssl>
                <truststore location="keystore.jks" password="password" />
             </ssl>
        </target>
    </serviceProxy>

Http call duration is aroud 13 seconds. The service is not return error after 5 seconds.
I give up. Maybe I am the only one that need this ?

[predic8]

Hi @cristianmusat,
sorry somehow I missed your post. We'll have a look at it. Hope it is not too late.
Thomas

[cristianmusat]

Hi Thomas,
It is not to late. Maybe you can check what I say. Thank you.

[rrayst]

Hi @cristianmusat , this is indeed a bug.

The documentation of the timeout attribute is incorrect: It says "Socket timeout (connect, read, etc.) in milliseconds." but in reality it is "Socket timeout (connect) in milliseconds." only, unfortunately.

read() operations on the HttpClient's socket are currently not time-limited. We will introduce an additional attribute soTimeout with the next release (see #1605). With the next release you could use

  <serviceProxy name="TestService" port="80">
        <path>/gateway/services/test</path>
        <wsdlRewriter />
        <wsdlPublisher wsdl="/opt/api-gateway/conf/wsdl/test/test.wsdl"/>
        <httpClient>
           <httpClientConfig maxRetries="1">
               <connection keepAliveTimeout="4000" timeout="5000" soTimeout="3000" />
           </httpClientConfig>
        </httpClient>
        <target url="https://test-service.anydomain.local/webservice">
              <ssl>
                <truststore location="keystore.jks" password="password" />
             </ssl>
        </target>
    </serviceProxy>

This would mean that the service has 3 seconds to respond.

(Please note, that none of the timeouts limit the "over all time taken by your backend to respond". Instead, soTimeout limits the "time a network read() call waits for any network data to arrive before throwing an Exception".

Therefore, if your backend would "send <, wait 1 second, send s, wait 1 second, send o, wait 1 second, send a, wait 1 second, send p, wait 1 second, send :, wait 1 second, send E, wait 1 second, send n, wait 1 second, send v, wait 1 second, send e, wait 1 second, send l, wait 1 second, send o, wait 1 second, send p, wait 1 second, send e, etc." instead of "wait 13seconds, send <soap:Envelope etc., Membrane would not return a HTTP status code 500 after 3 seconds but wait for the complete HTTP response. But this problem is mostly theoretical, as you most definitely observe the second behaviour.)