[GitHub] gyoetam opened a new pull request #466: fix: handle connectionRequestTimeout in AsyncHTTPConduitFactory

[GitBox <gi...@apache.org>]

gyoetam opened a new pull request #466: fix: handle connectionRequestTimeout in AsyncHTTPConduitFactory
URL: https://github.com/apache/cxf/pull/466
 
 
   Motivation: if connections are contended towards a slow target, it may make sense
   to set connectionTimeout and connectionRequestTimeout to values much lower than
   the receiveTimeout. Expected client behavior is to receive an error if a connection
   does not become available within connectionRequestTimeout. Current behavior however
   is that the error is only received after up to receiveTimeout has passed, when a
   current request to the target has finished and the connection is released or returned
   to the pool.
   
   Fix: instead of only checking expired leases when a connection becomes available,
   periodically check them in the same thread that checks idle connections as
   well. This makes sure that an error is returned to the client after
   a maximum of connectionRequestTimeout + selectTimeout.
   
   As a side effect, PoolingNHttpClientConnectionManager logs a debug level message
   at every selectTimeout interval - this should be suppressed by the logging framework.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services