MetaData Aggregator Socket Time Outs

[Dan McLaughlin]

Has anyone found a workaround for this timeout issue?

--

Thanks,

Dan McLaughlin
Technology Consortium, LLC
dmclaughlin at tech-consortium.com
mobile: 512.633.8086
http://www.tech-consortium.com

NOTICE: This e-mail message and all attachments transmitted with it
are for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is strictly prohibited. The contents of
this e-mail are confidential and may be subject to work product
privileges. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.


On Tue, Sep 23, 2014 at 11:10 AM, Ian Young <ian at iay.org.uk> wrote:
>
> On 22 Sep 2014, at 14:48, Ian Young <ian at iay.org.uk> wrote:
>
>> On 22 Sep 2014, at 14:28, Kaspar Brand <kaspar.brand at switch.ch> wrote:
>>
>>> 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.
>>
>> Thanks for pointing this out. In fact both of those 5-second timeout values seem rather aggressive to me.
>>
>> I'm not sure why HttpClientBuilder is imposing Shibboleth-local defaults at that level (particularly such short ones) rather than letting the lower level system defaults show through. Maybe we shouldn't be doing that (in HttpClientBuilder).
>
> I opened a case for this:
>
>         https://issues.shibboleth.net/jira/browse/JSPT-48
>
> Cheers,
>
>         -- Ian
>
>
>
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net