OUD Proxy: Failover Failing Every 15 Minutes with "java.nio.channels.ClosedChannelException" Error
(Doc ID 1956174.1)
Last updated on OCTOBER 04, 2021
Applies to:
Oracle Unified Directory - Version 11.1.2.2.0 and laterInformation in this document applies to any platform.
Symptoms
Architecture:
2 x OUD proxy, round robin DNS. OUD 11gR2 11.1.2.2.0
2 x OUD servers. OUD 11gR2 11.1.2.2.1
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>/<LOCALHOST>:<ADMIN_PORT>)) } method={sendLDAPMessage(LDAPClientConnection.java:978)} caught={java.nio.channels.ClosedChannelException}
Stack Trace:
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:265)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:474)
at org.opends.server.protocols.ldap.LDAPClientConnection$TimeoutWriteByteChannel.write(LDAPClientConnection.java:125)
at org.opends.server.extensions.RedirectingByteChannel.write(RedirectingByteChannel.java:100)
at org.opends.server.extensions.RedirectingByteChannel.write(RedirectingByteChannel.java:100)
at org.opends.server.protocols.asn1.ASN1ByteChannelWriter.flush(ASN1ByteChannelWriter.java:283)
at org.opends.server.protocols.ldap.LDAPClientConnection.sendLDAPMessage(LDAPClientConnection.java:956)
at org.opends.server.protocols.ldap.LDAPClientConnection.sendResponse(LDAPClientConnection.java:639)
at org.opends.server.core.SearchOperationBasis.sendSearchResultDone(SearchOperationBasis.java:933)
at org.opends.server.core.SearchOperationBasis.run(SearchOperationBasis.java:1632)
at org.opends.server.extensions.TraditionalWorkerThread.run(TraditionalWorkerThread.java:166)
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |