You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2006/07/27 23:45:20 UTC

[jira] Closed: (DIRSERVER-681) Memory leak in ADS ?

     [ http://issues.apache.org/jira/browse/DIRSERVER-681?page=all ]

Emmanuel Lecharny closed DIRSERVER-681.
---------------------------------------

    Resolution: Fixed

Seems to be a false alarm. The memory should be carrefully set when using huge caches.

> Memory leak in ADS ?
> --------------------
>
>                 Key: DIRSERVER-681
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-681
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3
>            Reporter: Emmanuel Lecharny
>            Priority: Blocker
>
> When doing thousands of searches, at a point, the memory get exhausted, and the server stop to deliver responses.
> The first bet is that we have a memory leak somwhere. Using yourkit shows that the heap increase continuously while search requests are being processed.
> However, I have done an extensive test whith all cache set to 1, and launched an heavy test (100 000 random search requests over a 10 000 entries base), with a Heap size set to 25 M, and everything is running fast (even if it's slow).
> So the second bet would be that cache setting is to big in regard to the allocated memory, and we just exhaust memory using too much cache.
> I will try to do a 12H test with 1 sized cache tonite, and a 48H test with 100 sized cache on tuesday and wenesday, to check which hypothese is the good one (hope the second will be it :).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira