DPS Resource Limits Policy for Connection-idle-timeout Setting Not Enforced Correctly
Last updated on DECEMBER 08, 2016
Applies to:Oracle Directory Server Enterprise Edition - Version 126.96.36.199.0 to 188.8.131.52.2 [Release 11gR1]
Oracle Directory Server Enterprise Edition - Version 184.108.40.206.160719 to 220.127.116.11.160719 [Release 11gR1]
Information in this document applies to any platform.
Setting an unlimited connection idle timeout limit through a resource limits policy does not work. Instead, the connection is disconnected after a few seconds of inactivity (usually 2 to 3 seconds) and the message "connection idle time-out has expired" is output to the DPS access log...
[05/Sep/2014:10:32:10 +0200] - OPERATION - INFO - conn=45 DISCONNECT
[05/Sep/2014:10:32:10 +0200] - DISCONNECT - INFO - conn=45 reason="admin limit exceeded" msg="connection idle time-out has expired "
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