Shib IdP 2.4.4 Issue
cantor.2 at osu.edu
Thu May 7 14:36:23 EDT 2015
On 5/7/15, 2:00 PM, "Michael A Grady" <mgrady at unicon.net> wrote:
>Be sure that your Tomcat/servlet container setup includes at least the minimum memory settings specified here:
>We were sure those settings were in place on one instance, but they weren't, and that was causing a failure when trying to update a large feed like InCommon's. You could see the update start to take place in the logs (with the metadata logging set to DEBUG), and it would just never complete. And in failing, it even killed the timer getting reset to ever check that feed again.
Yes, but that's what we patched, it should be trapping that now. If nothing else it should be visible. If not, that's probably a good thing because it would mean the problem's still "simple" and we just didn't manage to handle it yet.
> Didn't impact any other feeds, or the IdP in any other obvious way. (I assume there were messages in the Tomcat log, but didn't have access to those.) But we also didn't have the latest point release of the IdP, so maybe the behavior of 2.4.4 would be different.
It's supposed to be, and the working theory was that the growth had finally started hitting the heap limits people had set and so that was why it seemed like it "suddenly" became a bug. But then we patched it and it hasn't seemed to help...
More information about the users