Evidence of Resource Leak?

[Marvin Addison]

I recently updated to the 3.0 release version in our dev environment and
was working on getting springResource working for our LDAP data connectors
in attribute-resolver.xml. The IdP was last restarted on Friday, and I got
on this morning to find the host nearly dead from resource exhaustion: I
could barely log on and the CPU was over 100% (VM accounting artifact),
memory usage was high, and my shell was out of file handles. Fortunately,
killing the java process cleared things up.

The idp-process.log [1] file shows that OOM errors appeared shortly after
startup: IdP startup at 10:33:56, first OOMError at 10:58:49. I had been
running a pretty-close-to-3.0 snapshot for several weeks prior with no
problems, but I made some notable configuration changes along with the
upgrade to 3.0 release:

- Refactored attribute resolver config to use springResource
- logback logging for jetty

You can see from the log file that the LDAP pools were having trouble
initializing; I have no idea why. My concern is that there's some resource
that one of the reloading services is holding on to. File handle exhaustion
seems to suggest that files or sockets are included in the set of held
resources.

M

[1]
https://drive.google.com/file/d/0Bz3YRk8WRdWraTQ4R01iaHM5MTA/view?usp=sharing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20150210/71ccb78b/attachment.html