Le 18/12/2017 à 09:53, Maslova Polina a écrit :
> Dear Jiajia!
>
> In the kdcinit log I have this
>
> 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:2288}-Search successful
> : MessageType : SEARCH_RESULT_DONE
> Message ID : 2
> Search Result Done
> Ldap Result
> Result code : (SUCCESS) success
> Matched Dn : ''
> Diagnostic message : ''
>
> 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:511}-Removing <2,
> org.apache.directory.ldap.client.api.future.SearchFuture>
> 2017-12-18 10:10:11 DEBUG{SearchCursorImpl.java:210}-Closing SearchCursorImpl
> org.apache.directory.ldap.client.api.SearchCursorImpl@74650e52
> 2017-12-18 10:10:11 DEBUG{SearchCursorImpl.java:225}-Closing SearchCursorImpl
> org.apache.directory.ldap.client.api.SearchCursorImpl@74650e52
> 2017-12-18 10:10:11 INFO{LdapIdentityBackend.java:129}-closed connection
> with LDAP.
> 2017-12-18 10:10:11 DEBUG{AbstractIdentityBackend.java:112}-stop called
> 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:777}-received a NoD,
> closing everything
>
>
> at the end of the log.
>
> Is it a problems with Apache Directory?
Clearly, no.
The server just send you a SearchResultDone, which is the normal
response when a search request has been processed. We don't have any
information about how may entries have been sent back, as the log have
been truncated just before the SearchResultDone (it would be interesting
to get the previous logs, especially the ones where the searchRequest is
done, and the result entries returned, if any). However, again, this is
an expected response.
The LDAP API client then close the search cursor, as expected when the
search has been processed fully.
What would be interesting is to know why the LdapIdentityBackend class
closed the LDAP connection (this is a Kerby class, it's in teh doStop()
method, and it seems that the close was properly handled).
Jiajia ?
--
Emmanuel Lecharny
Symas.com
directory.apache.org
