directory-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/DIRAPI-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662488#comment-13662488
] 

Emmanuel Lecharny commented on DIRAPI-140:
------------------------------------------

Weird...

I receive an ExtendedResponse in the middle of the loop :

...
Waiting for 30
Message ID :30 for SearchResultEntryDecorator
Message ID :30 for SearchResultDoneDecorator
Loop 21
Waiting for 31
Message ID :31 for SearchResultEntryDecorator
Message ID :31 for SearchResultDoneDecorator
Loop 22
Waiting for 32
Message ID :0 for ExtendedResponseDecorator

(Here, the number is the message ID, and we always wait for a SearchRequest)
                
> Test ClientSearchRequestTest.testSubDn() fails
> ----------------------------------------------
>
>                 Key: DIRAPI-140
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-140
>             Project: Directory Client API
>          Issue Type: Bug
>         Environment: Apache Maven 3.0.5 (rNON-CANONICAL_2013-02-25_10-23_root; 2013-02-25
11:23:59+0100)
> 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 searchCursor.next() 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: http://www.atlassian.com/software/jira

Mime
View raw message