DPS Becomes Unresponsive and Only Processes CONNECT and BIND Requests

(Doc ID 2323901.1)

Last updated on NOVEMBER 09, 2017

Applies to:

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

Symptoms

Directory Proxy Server becomes unresponsive, but continues to accept incoming CONNECT and BIND requests. The DPS process shows little to no CPU utilization. The DPS access log shows that incoming connections continue to be reported, but no further LDAP activity is logged...

[19/Jul/2017:11:30:32 -0500] - PROFILE - INFO - conn=3023779 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[19/Jul/2017:11:30:32 -0500] - CONNECT - INFO - conn=3023779 client=nnn.nnn.nnn.nnn:58048 server=example.com:2636 protocol=LDAPS
[19/Jul/2017:11:30:33 -0500] - PROFILE - INFO - conn=3023780 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[19/Jul/2017:11:30:33 -0500] - CONNECT - INFO - conn=3023780 client=nnn.nnn.nnn.nnn:42848 server=example.com:2636 protocol=LDAPS
[19/Jul/2017:11:30:33 -0500] - PROFILE - INFO - conn=3023781 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[19/Jul/2017:11:30:33 -0500] - CONNECT - INFO - conn=3023781 client=nnn.nnn.nnn.nnn:43456 server=example.com:2636 protocol=LDAPS
[19/Jul/2017:11:30:34 -0500] - PROFILE - INFO - conn=3023782 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[19/Jul/2017:11:30:34 -0500] - CONNECT - INFO - conn=3023782 client=nnn.nnn.nnn.nnn:59588 server=example.com:2389 protocol=LDAP
[19/Jul/2017:11:30:34 -0500] - PROFILE - INFO - conn=3023783 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[19/Jul/2017:11:30:34 -0500] - CONNECT - INFO - conn=3023783 client=nnn.nnn.nnn.nnn:55938 server=example.com:2389 protocol=LDAP
[19/Jul/2017:11:30:34 -0500] - PROFILE - INFO - conn=3023784 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config

If the unresponsive event is allowed to continue without manual administrative intervention, then the DPS errors log may eventually report the following message...

[19/Jul/2017:12:01:59 -0500] - PROCESSING - WARN - WorkerQueue full. Suspending connection handlers

Jstack data captured during an unresponsive event reveals that all DPS worker threads are "stuck" in the same state...

"Worker Thread 447" prio=10 tid=0x00007f2e7c948800 nid=0x19222 in Object.wait() [0x00007f2e17d3d000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at com.sun.directory.proxy.server.ClientOperation.waitUntilAbandoned(ClientOperation.java:1337)
- locked <0x00000007c1006a90> (a java.lang.Object)
at com.sun.directory.proxy.server.ClientConnection.canBindProceed(ClientConnection.java:677)
at com.sun.directory.proxy.server.BindOperation.processOperation(BindOperation.java:181)
at com.sun.directory.proxy.server.WorkerThread.runThread(WorkerThread.java:172)
at com.sun.directory.proxy.util.DistributionThread.run(DistributionThread.java:213)

Locked ownable synchronizers:
- None

Changes

 

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