Shib IdP 2.4 metadata refresh bug?

[Cantor, Scott]

On 4/20/15, 8:38 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:


>
>Yes.  If it's anything less than the latest 2.4.4, then you get into the 
>issues with the shared Timer and HttpClient timeouts.  Anything less than 
>2.4.1 you also have issues with certain types of exceptions/errors not 
>being caught (below).

I forgot about the timeout issue. While I've never seen that with my own 
IdP and InCommon's metadata, a hung connection seems to fit that log if 
the version was earlier than the latest (which just came out, so that's 
likely).

>Well, maybe, but we have literally been on the exact same version of 
>commons-httpclient (v3.1) for the entire life of the 2.x IdP.  B/c it's 
>dead ... so there was nothing to upgrade.    So there haven't been any 
>changes in that library that would have caused anything to change in the 
>IdP behavior, as far as I can see.

Was thinking something more environmental in Java that caused the library 
to regress, but as you say we apparently added the trap and logging to the 
old code anyway.

Still seems odd to me, there were hardly any reports of this kind of 
problem for a really long time.

-- Scott