Shibboleth IdP 3.2.1 on Windows 2012r2

[Cantor, Scott]

> Any recommendations for what we should do to take a closer look and/or to
> provide useful diagnostics to determine if there is some sort of memory
> leak? One thing I'v never been is a Windows sys admin, but they have some
> folks that can take a closer look.

No idea. My insight into Java's memory usage is pretty much "hope it works" and in 12 years running Shibboleth in production, it always has except for some recent issues with heap size due to the metadata growth. So I have never had to dig any deeper. Not using Terracotta helped with that.

> Would frequency of looking for changed config files have any impact?

That would be an obvious issue to look at. It can't be metadata, because everybody has that.

> We did have this IdP accessing a remote filter file  (in addition to its local one) thru
> HTTPS (using SWITCH config as an example), but we turned that off just in
> case that was having any impact. But the behavior stayed the same, with the
> growth.

That would have been my guess, so that doesn't leave much. I think the most productive thing to find out is the answer to my original question. If others are running it on this OS, then that proves the problem is local.

I don't think it's possible to be using a different XML parser without having errors, but looking for copies of Xerces might be worth a minute or two.

-- Scott