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)

Last updated on APRIL 10, 2017

Applies to:

Oracle Directory Server Enterprise Edition - Version 6.3 SP1 and later
Information in this document applies to any platform.
***Checked for relevance on 30-Jul-2014***

Symptoms


On : 6.3.1 SP1 (6.3.1.1) version with a combo hot fix value of

(6.3.1.1_CUMUL_2010_11_08+6979489+6979533+
CONN_STATS+DATE_WITH_MILLISECS B2010.1130.1542) or later, Configuration



When attempting to retrieve a 2Mb+ entry, the following error occurs.

ERROR
-----------------------
DISCONNECT - INFO - conn=24779 reason="admin limit exceeded" msg="client didn't read any data during 160 milliseconds."



Steps To Reproduce:
--------------------------

1) Hotfix combo as noted in top of this note.
2) DPS needs to have the handler configuration "close-client-connection" set to "true", as default is "false".

dpconf set-connection-handler-prop [-h host] [-p port] CONNECTION-HANDLER-NAME PROP:VAL

This property is a flag indicating whether or not the connection
handler should close the client connection when no data source is available.

3) Restart DPS
4) Create an entry with an attribute value 2Mb+ in Directory Server
5) Use ldapsearch to search for the entry through DPS 6.3.1.1
6) Check the DPS error logs


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot retrieve entries with large (usually binary) attribute values, e.g. Certificate Revocation Lists.

Changes

1)

Combo Hotfix value at least
(6.3.1.1_CUMUL_2010_11_08+6979489+6979533+
CONN_STATS+DATE_WITH_MILLISECS B2010.1130.1542) or later, Configuration



2) DPS needs to have the handler configuration "close-client-connection" set to "true", as default is "false".

dpconf set-connection-handler-prop [-h host] [-p port] CONNECTION-HANDLER-NAME close-client-connection:true

This property is a flag indicating whether or not the connection
handler should close the client connection when no data source is available.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms