LDAPUX and ldapclientd connection pool

[Jonas Lindén]

In our directory server we have set the idletimeout = 30, i.e idle connection are dropt after 30 seconds. I've found that the ldapclientd daemon dosen't test the connection in the LDAP connection pool before returning a connection. The workaround for this is to set the connection_ttl to a low value, I've set it to 10.

Is this a known bug?

[Steven E. Protter]

Shalom,

If its a bug its not known to me.

Make sure you are using the latest version of ldap-ux from http://software.hp.com

LDAP-UX does not normally get bug fixes like the Core OS. HP releases new software.

If this is an OS issue, your system should be patched to a recent bi-annual update.

I'd like to see how you reached this conclusion:
>>
I've found that the ldapclientd daemon dosen't test the connection in the LDAP connection pool before returning a connection.
<<

You might have a network configuration issue with regards to close_wait, see /etc/rc.config.d/nddconf

SEP

[Jonas Lindén]

Steven,

We are running the LDAP-UX Client B.04.17 on HP-UX 11v3 with the latest patches. We intermittenly get errors like "Invalid user xxx" when doing ssh login and "nsquery passwd xxx ldap" is failing occasionally.
If we remove the idletimeout = 30 property setting in our directory server the problem dissappears. So my guess is that the ldapclientd daemon does not make any check that an unbound connection from the pool is used. The workaround to clean up idle connections in the pool every 10 seconds (connection_ttl=10) also solves the problem.
Still, you might be right. I't could be a network configuration issue.

Thanks,
Jonas