LDAP "ServerListener" stops responding (Max number of connections reached)

Question

Hi --
The last four work days, in the evening, our OAS 10G server stopped processing portal logon requests. The response to login requests was this message:
Internal error WWC-00006 Unexpected error
encountered in wwsec_app_priv.process)signon
(User-Defined Exception) (WWC-41417)
An exception was raised when accessing the
Oracle Internet Directory 81: Can't contact
LDAP server. Details:
Operation dbms_ldap.simple_bind_s (The message also included other details such as the host, port and DN, and a reference to error message WWC-41743.)
Suspecting an LDAP problem, we looked on the server, and in ORACLE_HOME/LDAP/LOG I found recent log files (oidldapd[instance]s[pid].log) with several megs of messages that look like this:
2005/06/17:17:59:33 * ServerListener :2 * ERROR :
ServerListener : Max numbers of connections reached.
Num Conns = 874, Max Conns = 874, Closing the
connection. These messages repeated, several times per minute, overnight and the next day until I restarted the server. The same thing happened again the next night.
A metalink search pointed to docid "293391.1" which, in part, suggests that the problem may be caused by improper programming, and that the solution may be to, "investigate the applications that connect to OID and where possible modify them to perform an explicit disconnect."
Does anyone have any reference to how an application can perform an explicit disconnect from the OID? We do have a relatively new application which follows the "Java API for Oracle Internet Directory" -- documention found here: http://download-west.oracle.com/docs/cd/B10501_01/network.920/a96577/oid_java.htm -- but in that document we cannot find any reference for how to "perform an explicit disconnect".
The application already calls the "context.close()" method, which according to the documentation closes the connection to the OID, but we cannot find any other "explicit disconnect". And, since the problem happens even though our app is already calling the context.close(), there must be something else.
Opened this up as a Metalink question related to Portal, but they said it's not their problem, and we should ask over here.
Any thoughts?

Answer 1

Looks like that's helped. While the errors persist, OID isn't dieing.
For anyone with similar problems, it looks like docid 437493.1 is useful. Upgrade clients to at least 10.2.0.3 to defeat a sqlnet problem.
Just tried it with the 10.2.0.5 patchset and it seems to be working and not generating the 104 error on the OID server.