directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] [Commented] (DIRAPI-140) Test ClientSearchRequestTest.testSubDn() fails
Date Tue, 21 May 2013 00:13:17 GMT


Emmanuel Lecharny commented on DIRAPI-140:

More specifically, I get a NotoceOfDisconnection :

Received an extended response :MessageType : EXTENDED_RESPONSE
Message ID : 0
    Extended Response
        ResponseName :''
        Ldap Result
            Result code : (SUCCESS) success
            Matched Dn : 'null'
            Diagnostic message : 'null'

which explains why the test fails.

Now, I see only one reason for the server to generate such an extendedResponse : an exception
has occured on the server.
> Test ClientSearchRequestTest.testSubDn() fails
> ----------------------------------------------
>                 Key: DIRAPI-140
>                 URL:
>             Project: Directory Client API
>          Issue Type: Bug
>         Environment: Apache Maven 3.0.5 (rNON-CANONICAL_2013-02-25_10-23_root; 2013-02-25
> Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.9.2-1-arch", arch: "amd64", family: "unix"
>            Reporter: Stefan Seelmann
> In trunk the test ClientSearchRequestTest.testSubDn (module ldap-client-test) fails quite
often. When adding a for loop around the test code it fails after 1-10 executions. The first
search works always, but the second search which uses the SearchRequest object sometimes doesn't
contain a result and is false. Please note that I'm not sure if that is
a pb in client or in the server.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message