Shib IdP 2.4 metadata refresh bug?

[Cantor, Scott]

On 4/20/15, 12:06 PM, "Michael A Grady" <mgrady at unicon.net> wrote:

>I've been trying to help someone running IdP 2.4

2.4.what? If it's not the latest, that's step 1.

> / Tomcat 6 on Windows 2008 R2 with a problem where the InCommon metadata is not refreshing. After ruling out all other reasons for it not to be refreshing, and turning on debug for metadata, I see where the check for InCommon metadata was happening just fine, until it seemed to reach a point where, during an update of that metadata, the timer went off for a refresh of its own (idp-metadata.xml) file. Which seemed to not only "stomp on" the current refresh of the InCommon metadata, but also prevent a new timer being set for the next update, so subsequent to the below, there was never again a check to see if the InCommon metadata needed updating. See log lines at end of this note.

I doubt it's related, it's just failing the InCommon update task and eventually it runs the other one (they're 45 minutes apart aren't they?)

I'm starting to believe given the number of people who have suddenly started having issues that the old and now dead HttpClient library used by V2 has a regression that ended up creating exceptions that used to be handled more appropriately. Either way, the latest patches reduced the potential overlap between refresh tasks so that the problems are more confined, but it's still a single threaded timer with not much chance of recovering from issues. I don't know what the logging looks like. V3 has a more aggressive catch clause for Throwable now to log problems, don't know that V2 does.

Before I spent a lot of time on root causes, I'd just increase the heap size if it's not set to a reasonable number.

-- Scott