[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Memory leak, crash & weird results

I don't think so because of the way my app is done.  I have a small pool of connections to openldap (5 connections actually) and all the database requests are made through those connections so I never have more than 5 connections open to the database.  Do you think it can be due to configuration problems?  I have a lot of custom objects and attributes and my previous experiences with directory servers were with iPlanet Directory Server so I'm not quite familiar with defining as much stuff. 
By the way, did you use slapd as a service or run it in a window? 
----- Original Message -----
Sent: Friday, October 12, 2001 5:21 PM
Subject: RE: Memory leak, crash & weird results

I'm running 2.0.7 from Fivesight (though I've tested 2.0.11 as well) on 2000 (and used to run it on NT).  I've never had such problems -- although in my case the load is relatively small.  One thing to note for the Fivesight build, is that the maximum number of concurrent connections is 64 (after which, connection requests are denied) -- so could it be that it's your client(s) fault?
-----Original Message-----
From: Stéphane Cloutier [mailto:scloutier@coginetwork.com]
Sent: Friday, October 12, 2001 2:21 PM
To: openldap-software@OpenLDAP.org
Subject: Memory leak, crash & weird results

I've install the FiveSight Technologies build of OpenLdap for windows (http://www.fivesight.com/downloads/openldap.asp).  I've try their build of version 2.0.7 and 2.0.11 on windows NT and 2000 and got a lot of weird problems using them.  With all OS / OpenLdap version combination, I've got some or all the following problems:
-    After rebuilding the indexes with slapindex utility, I have less entries in the directory than it should.  Searches return less entries than it suppose to.
-    OpenLdap memory seems to grow constantly with activity until it crashes.
-    Sometimes, unless no crash seems to happen and the connection still seems to be ok, no more results are returned and no entry can be read from the directory unless I restart OpenLdap or even, recopy an old backup of the ldbm folder.
The two last points happens especially on a medium to high load.  Anybody have comments, suggestions or ideas on this?  I'm really suprised by those behaviors and haven't find a way to fix this, any help would be appreciated.