[
https://issues.apache.org/jira/browse/DIRAPI-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102036#comment-17102036
]
Emmanuel Lécharny commented on DIRAPI-358:
------------------------------------------
Ok, thanks for the context.
First, I would suggest you switch to 2.0.1 which has been released a few weeks
ago.
Regarding your issue, your pool will contain up to 64 connection, so it's
unlikely to swallow all the inodes on your system. what are the limits on your
system ? ({{ulimit}})
Also can you paste teh result of your lsof command ?
> File Descriptor leak on connection failure with LdapConnectionTemplate
> ----------------------------------------------------------------------
>
> Key: DIRAPI-358
> URL: https://issues.apache.org/jira/browse/DIRAPI-358
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 2.0.0.AM4, 2.0.0, 2.0.1
> Reporter: Natan Abolafya
> Priority: Major
>
> Seems to have appeared on AM4.
>
> We had two instances crashing after half an hour outage on the LDAP server
> because the process ran out of file descriptor limit.
>
>
> {noformat}
> var template = createLdapConnectionTemplate();
> template.searchFirst(....);
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
