The ContextSourceMonitor component allocates connections as part of its health check, but fails to close them. This produces a pernicious resource leak that can quickly cause an OOM condition under circumstances where this monitor is configured and the /status URI is an enterprise monitoring endpoint.
Environment
None
Activity
Show:
Marvin AddisonAugust 13, 2013 at 8:27 PM
Note that this issue does not affect 4.x since new ldaptive-based components supersede this and other monitors that use Spring LDAP.
The ContextSourceMonitor component allocates connections as part of its health check, but fails to close them. This produces a pernicious resource leak that can quickly cause an OOM condition under circumstances where this monitor is configured and the /status URI is an enterprise monitoring endpoint.