DS/DPS: DPS Error: "Unable to read SEARCH response from backend server : Connection closed by the peer backend server (EOF received)." DS Error: "B4 - Server failed to flush BER data back to client"
(Doc ID 1339963.1)
Last updated on APRIL 27, 2023
Applies to:
Oracle Directory Server Enterprise Edition - Version 6.3 SP1 and laterInformation in this document applies to any platform.
*** ***
Symptoms
The following error messages occur in the -
Directory Server (DS) access log:
-
B4 - Server failed to flush BER data back to client
Directory Proxy Server (DPS) access log:
-
Unable to read SEARCH response from backend server : Connection closed by the peer backend server (EOF received)
Explanation of B4 error message
From Connection Codes in Log Files -
The server failed to flush data response back to client. This code can occur when the client closes the connection to the server, before the server finished sending data to the client.
With DS/DPS deployment, this B4 DS error means that DPS has closed the connection with DS before DS has finished off sending data. Therefore DS is issuing this error message to indicate that DPS has closed the connection abruptly
Checking the correlation of DS and DPS error messages
DS access logs:
[07/Jul/2011:16:36:03 +0200] conn=31 op=2 msgId=4 - SRCH base="o=GROUP-1,dc=SUFFIX_DN" scope=2 filter="(computerInfo=OR-LEG_*)" attrs="objectClass subschemaSubentry objectClass subschemaSubentry"
[07/Jul/2011:16:40:04 +0200] conn=31 op=2 msgId=-1 - closing from X.Y.Z.T:52601 - B4 - Server failed to flush BER data back to client -
[07/Jul/2011:16:40:04 +0200] conn=31 op=-1 msgId=-1 - closed
DPS access logs:
[07/Jul/2011:16:36:03 +0200] - SERVER_OP - INFO - conn=12 op=2 SEARCH base="o=GROUP-1,dc=SUFFIX_DN" scope=2 filter="(computerInfo=OR-LEG_*)" attrs="objectClass subschemaSubentry objectclass subschemaSubentry " s_msgid=4 s_conn=rmx150107:36
[07/Jul/2011:16:40:07 +0200] - OPERATION - INFO - conn=12 op=2 SEARCH RESPONSE err=1 msg="Unable to read SEARCH response from backend server : Connection closed by the peer backend server (EOF received)." nentries=13932 etime=243953
It is very important to establish the correlation between a given DS and DPS request, and to follow exactly how DPS is handling it.
Here it is also worth noticing that this request (which is failing) is returning a very large number of entries since the filter will match many entries (where the number of entries is the value of nentries in the DPS SEARCH RESPONSE line above).
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 |
Explanation of B4 error message |
Checking the correlation of DS and DPS error messages |
Cause |
Solution |