OUD - Connection Errors Filling Up Log - "caught={javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?}"
(Doc ID 2736473.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Unified Directory - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Symptoms
OUD logs are filled with connection errors.
In OUD debug log -
caught error thread={LDAP Request Handler x for connection handler LDAP Connection Handler 0.0.0.0 port <ADMIN_PORT>(57)} threadDetail={parentThread=main(1) isDaemon=false } method={finalizeClientConnection(LDAPClientConnection.java:1234)} caught={javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?}
In server.out -
LDAP Request Handler x for connection handler LDAP Connection Handler 0.0.0.0 port <ADMIN_PORT>, fatal error: 80: Inbound closed before receiving peer's close_notify: possible truncation attack?
javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
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 |
Cause |
Solution |
References |