MetaData Aggregator Socket Time Outs

[Kaspar Brand]

On 19.09.14 23:21, Ian Young wrote:
> There's no known issue in the MDA itself, no. When this has happened,
> as far as I know it's always been down to a transient network failure
> or a failure of the server you're referencing to respond. In other
> words, genuine timeouts.
> 
> You can tweak the timeout, but that would only help if the problem
> was that the server was overloaded and slow to respond. It's not a
> good solution even then.

I think that the socketTimeout set in [1] is a tad too aggressive. A
connect timeout of 5 seconds is fine, but I would increase the default
for the "idle" timeout to something between 30 and 60 seconds.

In the case of mds.edugain.org (and its dynamically generated metadata)
e.g., we definitely had to increase the socketTimeout, otherwise we had
been increasingly running into timeouts earlier this year.

Kaspar

[1]
http://svn.shibboleth.net/view/utilities/java-support/trunk/src/main/java/net/shibboleth/utilities/java/support/httpclient/HttpClientBuilder.java?view=markup