I'm getting these
exceptions from the JNDI/SPI (from sun) connecting to an iPlanet Dir Server
5.0. And I get them under pretty lightly
loaded scenarios.
As I understand it,
this maps to one of LDAP error codes 51 (busy) or 52 (unavailable). I only have
50 connections being created during about 45 seconds and only 10 concurrent
threads doing a total of 641 reads. So this is a very light load and I'm
supprised that the server could be busy or unavailable.
I've also noticed
have noticed a big difference between our dir server running on a
Solaris box and the one on my NT workstation. Believe it or not, the test
on my NT workstation can survive for much longer (15
minutes) than when run against the UNIX server before encountering the
error.
So it appears to be
a problem at the LDAP server. Perhaps some tuning I need to do. But I
would assume the server could handle such lite loads with the out-of-the
box setttings.
Any ideas
anyone?
Jonathan McClure
Software
Architect
Wheelhouse Corporation
35 Corporate Drive | 3rd
Floor
Burlington, MA 01830
phone 781.505.3205 | fax
781.505.3001
www.wheelhouse.com
