[ 
https://issues.apache.org/jira/browse/DIRSERVER-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Norval Hope updated DIRSERVER-1161:
-----------------------------------

    Attachment: mina_1.1.2_streaming.patch
                installers_1.5.1_streaming.patch
                apacheds_1.5.1_streaming.patch

Unfortunately the problem persists against the 1.5.1 tagged release too, the 
attached files are patches to the top-level component after which they are 
named, with my source tree as follows:

<top>/
   apacheds/ (checked out from 
http://svn.apache.org/repos/asf/directory/apacheds/releases/1.5.1)
   installers/ (checked out from  
http://svn.apache.org/repos/asf/directory/installers/releases/1.5.1)
   mina/ (checked out from http://svn.apache.org/repos/asf/mina/tags/1.1.2)

I'll include the top-level POM I used (cut-down version of the on one from the 
trunk) and sample logging output in next attachments.

> search results are not streamed to the client until final done response is 
> queued
> ---------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1161
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1161
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0
>         Environment: JDK 1.5.0_11 
>            Reporter: Norval Hope
>         Attachments: apacheds_1.5.1_streaming.patch, 
> installers_1.5.1_streaming.patch, mina_1.1.2_streaming.patch, 
> streaming_log_output.txt, streaming_logging.patch
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Search results accumulate in Events on the SessionBuffer.eventQueue within 
> ExecutorFilter.fireEvent() until final done response for the search is 
> written to the session and then all results for the search (possibly millions 
> depending on the search and state of the directory) are written out at once. 
> This is a big problem for scalability and I gather from previous 
> correspondence with Alex that this behaviour is unexpected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to