[
https://issues.apache.org/jira/browse/DIRSERVER-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1620:
-----------------------------------------
Component/s: (was: ldap)
network
> Close Idle Connections after a certain timeframe has passed too prevent "Too
> many open files" error
> ---------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1620
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1620
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: network
> Affects Versions: 1.5.7
> Environment: Unix
> Reporter: Steve
> Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Regarding the following post
> http://mail-archives.apache.org/mod_mbox/directory-users/201102.mbox/%3c4d668ded.6020...@gmail.com%3e
> ApacheDS keeps connections open (im not certain its just idle connections,
> there might be another issue). After a while the number of open connections
> will exceed the OS default setting (Too many open files).
> The default is mostly 1024 and can be increased - but it should not be
> necessary when you have less clients/users than that.
> I have a user base with 500 outlook clients - after a while the Too many open
> files error occurs. Using netstat i filtered the LDAP connections and saw
> that they increased per client IP each day (not all) - some had up to 5-10
> connections per IP, in total there where however only 100 client IPs.
> I suggest that ApacheDS automatically cleans up idle or open connections
> after a while (timer task maybe?), it should also be aware of the current
> amount of open connections - in case a threshold is reached it should start
> cleaning up connections sooner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
