FYI: On the Windows platform running 6.5.4, we started experiencing the dreaded “Insufficient memory - Directory Manager pool is full” error again.
Lotus initially gave us an INI parameter as a workaround (to keep the pool from filling too quickly):
DIRMAN_POOL_SIZE=100 (restart is necessary)
We then received hotfix 102 for SPR JPAS6ALJQE.
Unfortunately, we put the INI parameter in last night on 11 servers and applied the hotfix on one server this morning so I can’t say if it worked or not. 
Subject: Insufficient memory - Directory Manager pool is full: Solutions
just wondering, do you have any ibm director software installed? one of the older versions has a memory leak and may be contributing to the problem.
we had the same issue, server barfed and when i looked it was using 3gb of ram, there was a task named pegsus… or something along those lines, it was part of ibm director remote control software, and it was usuing a horrendous amount of ram. upon removing the software and rebooting, the server went back to normal and we haven’t had any problems since.
i didn’t add the INI variable as i didn’t look at that side of things until later but it caused the same flow of errors
Entry already in index
ATTEMPT TO ACCESS DATABASE xxxx by User was denied
Insufficient memory - NSF directory manager pool is full.
each repeated several (hundred?) thousand times
Subject: RE: Insufficient memory - Directory Manager pool is full: Solutions
Same issue here.
I don’t have TDP, but it occurs (ao.) when I start the Administrator and go the the “files” overview.
Not always, though…
Subject: Did you solve it?
We have similar problem - Domino 6.5.4, Win2003. I think, that problem is in TDP (Tivoli Data Protection - backup software), because:a) there are 3 identical Domino servers in cluster, but just one with TDP has this issue…
b) I am aware of IBM SPR, that mentions backup solution as possible reason of changing working directory
So, my question: Did you solve this issue with DIRMAN_POOL_SIZE?
Subject: RE: Did you solve it?
Nope. We are still experiencing the issue. The INI parameter was only meant to slow the occurance of the problem, not solve it. 
We were given another INI parameter to put in to debug the issue and have been sending the console output to IBM for analysis.
It is interesting that you mention TDP, because we also use that and the last update I had from IBM is that a thread didn’t terminate that most likely came from a command line utility or other third party software using the Domino API. Hmmm…
Subject: Insufficient memory - Directory Manager pool is full: SOLVED
McAfee products were causing our issue. Some sort of interaction between ePO and GroupShield. We had to manually delete some .dlls to resolve the issue as McAfee couldn’t figure it out.
Subject: RE: Insufficient memory - Directory Manager pool is full: SOLVED
What were the dlls that you had manually deleted. We are experiencing NSF Directory Manager Pool is Full on several servers. IBM has not given resolutions. Please help
Subject: RE: Insufficient memory - Directory Manager pool is full: SOLVED
If you have GroupShield 5.3 and Domino 6.5.4, then McAffe has a knowledgebase article with a workaround, KB44573.
Subject: RE: Insufficient memory - Directory Manager pool is full: SOLVED
I can’t find the knowledge base article 44573. Do you have a copy somewhere you can send to me? This issue is still not resolved. Please help. Thanks.
Subject: RE: Insufficient memory - Directory Manager pool is full: SOLVED
Hi All,
We’re getting this today and I’m just wondering if a full fix has been found as opposed to a simple work around?