My Oracle Support Banner

OUD Proxy Ping-ponging - ClosedChannelException On OUD Server (Doc ID 1956174.1)

Last updated on OCTOBER 31, 2019

Applies to:

Oracle Unified Directory - Version and later
Information in this document applies to any platform.


  2 x OUD proxy, round robin DNS. OUD 11gR2
  2 x OUD servers. OUD 11gR2
  Load-balancing routes defined on OUD proxy.
  Red Hat Enterprise Linux Server release 6.4 (Santiago)

An OUD proxy is configured to load balance across two OUD servers. Every 15 minutes the proxy reports that the failover load balancing route for one OUD server has failed, and it switches to the other. This ping-pong behavior is causing problems with upstream applications.

The OUD server log reports a ClosedChannelException at the time the OUD proxy reports and error:

[23/Oct/2014:08:57:27 +1100] 112 caught error thread={Worker Thread 22(175)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from <IP>:<PORT> to <IP-2>:<PORT> operation=SearchOperation(connID=916, opID=482, baseDN=, scope=base, filter=(cn=ping from proxy <HOSTNAME>/ } method={sendLDAPMessage(} caught={java.nio.channels.ClosedChannelException}
Stack Trace:
 at org.opends.server.protocols.ldap.LDAPClientConnection$TimeoutWriteByteChannel.write(
 at org.opends.server.extensions.RedirectingByteChannel.write(
 at org.opends.server.extensions.RedirectingByteChannel.write(
 at org.opends.server.protocols.asn1.ASN1ByteChannelWriter.flush(
 at org.opends.server.protocols.ldap.LDAPClientConnection.sendLDAPMessage(
 at org.opends.server.protocols.ldap.LDAPClientConnection.sendResponse(
 at org.opends.server.core.SearchOperationBasis.sendSearchResultDone(



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.