My Oracle Support Banner

ODSEE11g: DPS Closes Connections with INFO: "client didn't read any data during 2560 milliseconds." for Normal Searches (Doc ID 2344030.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Oracle Directory Server Enterprise Edition - Version 11.1.1.7.160719 and later
Information in this document applies to any platform.

Symptoms

DPS closes connections with error: "client didn't read any data during 2560 milliseconds." for normal (non-admin) searches.

The connections are being closed even though "close-client-connection : false " is configured in DPS -

./dpconf get-connection-handler-prop -p 6389 -e -D "cn=xxxxx" "default connection handler" close-client-connection
Enter "cn=xxxxx" password:
close-client-connection : false

 

 

ERROR
-----------------------
reason="admin limit exceeded" msg="client didn't read any data during 2560 milliseconds."

If you increase the timeouts as per below notes
DPS 6.3.1.1 Can't Return Entry To Client DISCONNECT - INFO reason="admin limit exceeded" msg="client didn't read any data during 160 milliseconds." (Doc ID 1288955.1)

You get the same sequence and error, but with the new values

For example increasing from default 10 to 30:
pSearchzeroWriteSleepDelayInMilliSec: 30

you get the error with updated value:
DISCONNECT - INFO - conn=3 reason="admin limit exceeded" msg="client didn't read any data during 7680 milliseconds."


Due to this issue, "slow" clients connections are dropped.

 

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


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