LDAP + win2k3 = BPool Memory Error ...Please help!

HCL Domino Domino Forum
1

Hey Folks,

I’ve recently installed Domino 6.5 on win2k3 and set-up Directory assistance to run LDAP on this server. I’m not using AD, so it can bind to port 389 fine. At first I can connect after I reboot the server, but then after 10-20 tries of searching ldap records from my ldap client, it get an error in the client. I see the following on the server console when this happens:

tell ldap showconfig debug

01/19/2004 01:11:40 PM LDAP Server: Listening on TCP/IP port 389

01/19/2004 01:11:40 PM LDAP Server: Anonymous access over TCP/IP is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Name/Password (simple) authentication over TCP/IP is ENABLED

01/19/2004 01:11:40 PM LDAP Server: Maximum entries returned = 0

01/19/2004 01:11:40 PM LDAP Server: Time limit for search = 0 seconds

01/19/2004 01:11:40 PM LDAP Server: Minimum characters needed for wild card = 1

01/19/2004 01:11:40 PM LDAP Server: Return UTF8 results to LDAPv2 clients is ENABLED

01/19/2004 01:11:40 PM LDAP Server: Maximum referral URLs returned is 1

01/19/2004 01:11:40 PM LDAP Server: When there are multiple instances of an entry then Don’t Modify Any

01/19/2004 01:11:40 PM LDAP Server: Schema enforcement is ENABLED

01/19/2004 01:11:40 PM LDAP Server: Automatic FT indexing of domino directories on service startup is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Alternate language information processing is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Require distinguished name on bind is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Activity log truncates attribute values at 4096 bytes

01/19/2004 01:11:40 PM LDAP Server: Activity logging is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Mail-only type groups are never candidates in membership search requests

01/19/2004 01:11:40 PM LDAP Server: Batch adds are DISABLED

01/19/2004 01:11:40 PM LDAP Server: Pre-5.5 Outlook client behavior is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Loopback mode is DISABLED

01/19/2004 01:11:40 PM LDAP Server: Honor XACLs = ENABLED

01/19/2004 01:11:40 PM LDAP Server: Configuration sampling interval = 3 minutes

01/19/2004 01:11:40 PM LDAP Server: Debug trace logging level = 0x0

01/19/2004 01:12:40 PM Error attempting to access the Directory *GRANDVIEW.TECHFLOW.COM:389 (no available alternatives), error is LDAP BPool Full

01/19/2004 01:14:46 PM Directory Assistance is reloading internal tables due to remote server failure.

Any ideas? Could this be a compatibility issue. I also tried 6.0.3 too on another server even and that yeilds the same results.

TIA!

Lou

2

Subject: LDAP + win2k3 = BPool Memory Error …Please help!

I’ve recently installed Domino 6.5 on win2k3 and set-up Directory assistance to run LDAP on this server. I’m not using AD, so it can bind to port 389 fine.

When you say “setup DA to run LDAP on this server”, do you mean

You are running the Domino LDAP server, or

You have added a DA document with an LDAP source?

At first I can connect after I reboot the server, but then after 10-20 tries of searching ldap records from my ldap client, it get an error in the client. I see the following on the server console when this happens:

Your LDAP BPool Full message indicates that either the Domino LDAP server or something that uses the Domino LDAP SDK is leaking memory. Both the LDAP server and any apps that use our LDAP SDK on that same machine share the same memory pool.

Is the “my ldap client” which you mention an application which you wrote which calls the Domino LDAP SDK functions? If so, you’re probably missing the associated ldap_*_free calls that return memory.

BTW, there’s a one-page summary of common LDAP C SDK and JNDI directory calls at

“Collaborative Cuisine’s 1 Hour JNDI Cookbook”

http://www-10.lotus.com/ldd/sandbox.nsf/0/c46c671f7611110a85256df60078e910?OpenDocument

See LDAP_C_API_to_JNDI_Cheat_Sheet.html in cookbook.zip

Any ideas? Could this be a compatibility issue. I also tried 6.0.3 too on another server even and that yeilds the same results.

By “compatibility issue”, do you imply that your app used to work with some version of ND?