Can you send a snippet of the code that has the problem. It is not quite clear
which timeout you are referring to as the server timeout setting.
Miodrag
Johan Persson wrote:
> Hello,
>
> I am trying to use the Netscape's Java LDAP API to communicate with the
> iPlanet Directory Server v 5.0 and I am experiencing problems with the
> server timeout setting.
>
> If I set the server timeout value to 10 (ten) seconds,
> LDAPConnection.isConnected() still reports true well after the ten seconds
> (I have tested up to the one minute range) have expired. This is a big
> problem since I occasionally get LDAPExceptions when trying to use this
> connection after it should have timed out.
>
> I have tried the exact same Java code against another vendor's LDAP server
> and in that case the Java code works flawlessly
> (LDAPConnection.isConnected() reports false immediately when the connection
> is closed by the server) which leads me to the conclusion that the iPlanet
> server does not close the connections correctly. This is confirmed with a
> lot of open sockets on the machine that is running the LDAP server that are
> not being closed...
>
> Is this a known problem with iPlanet's directory servers (I get the same
> behaviour from Netscape's directory server 4.x)? As it is today, I do not
> see how we can use iPlanet's directory server.
>
> FYI, I am using the Windows version of the directory server in case this is
> a platform dependent problem.
>
> Thank you,
> Johan Persson
