Oidldapd Log Fills Up With Error: DispatcherListener: Unable to accept New TCP connection (Doc ID 275712.1)

Last updated on AUGUST 23, 2022

Applies to:

Symptoms

Oracle Internet Directory (OID).

OID dispatcher log, i.e., oidldapd01.log, fills up with "DispatcherListener: Unable to accept New TCP connection" errors, consumes all the available disk storage, then crashes OID (Oracle Internet Directory) and the server.

Excerpt of sample log:

These files, if not deleted regularly, can exceed into the GBs.

Scenario:
Load balancer (LBR) host (named ldap for example)
oid host1- <OID_HOSTNAME1> - full 9iAS or 10g infrastructure
oid host2 - <OID_HOSTNAME2> - OID only (typical install via Oracle Installer; not custom install)

All of a sudden, about 1-20 of the error message can be generated every ten seconds, and within a week the log files can grow to the point where the server crashes.

Using load balancer for reading only, writing always occur against one server (<OID_HOSTNAME1>) and then gets replicated to <OID_HOSTNAME2>.

There is hardly any traffic from a query standpoint, and very few users.

These errors messages appear on both servers, but on <OID_HOSTNAME1> is severe enough to cause server/OID crashes.


Similar issues were reported to Oracle Support in the past, and the following was reported as solution:
"Removing the load balancer and a second ethernet card out of the picture, assuming that it may be flooding with keepalive packets, and plugging the box with only one ethernet card directly into the router, the error goes away.
An external search for "Unable to accept New TCP connection" returns many hits, which lead to look at the router and load balancer which was sending and not acknowledging KeepAlive messages to the port that oidldapd is listening on."

Changes

Cause