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

Emmanuel Lecharny commented on DIRAPI-94:
-----------------------------------------

Interesting !

Now, we have to check that the AbandonRequest arrives *before* the entries have 
been transmitted to the user, otherwise it's normal that the user receives 
everything.

This version of the server computes all the results first, and fetch the 
entries one by one to send them to the client. It's a very fast operation 
(core-integ has some perf tests that demonstrates the server can fetch more 
than 160 000 entries per second). The set of returned entries must be big 
enough, and the abandonRequest must be sent fast enough for the AbandonRequest 
has a chance to be received and processed before it's completely sent. 

One possibility to check that the AbandonRequest is correctly processed is to 
add a MINA filter that slow down the sending of messages (or to add an entry 
Filter that does the same thing). Adding an interceptor that adds a Flter is 
also an option.
                
> Random failure of ClientAbandonRequestTest
> ------------------------------------------
>
>                 Key: DIRAPI-94
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-94
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M13
>            Reporter: Stefan Seelmann
>             Fix For: 1.0.0-M14
>
>
> ClientAbandonRequestTest.testAbandonSearch() fails occasionally on Jenkins. 
> To demonstrate it I added the MulitThreadedMultiInvoker, please run the test 
> with system properties "-Dmtmi.invocations=1000 -Dmtmi.trace=true" which runs 
> each test method multiple times. The problem is that sometimes the abandon 
> request has no effect but the client receives all search result. I'm not sure 
> if it is a problem is located in the client API or on the server side.

--
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

Reply via email to