You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Tong Fin (JIRA)" <ui...@incubator.apache.org> on 2008/08/12 18:32:44 UTC

[jira] Updated: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue

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

Tong Fin updated UIMA-1130:
---------------------------

    Attachment: DDE_PATCH_JIRA_1130_B.txt
                DDE_PATCH_JIRA_1130_A.txt

> Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue
> -----------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1130
>                 URL: https://issues.apache.org/jira/browse/UIMA-1130
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>    Affects Versions: 2.2.2
>            Reporter: Adam Lally
>         Attachments: DDE_PATCH_JIRA_1130_A.txt, DDE_PATCH_JIRA_1130_B.txt
>
>
> The Spring XML allows setting a concurrentConsumers property for a reply queue (either an aggregate's collocated reply queue or a remote reply queue):
>      <property name="concurrentConsumers" value="1"/>
> The deployment descriptor should allow setting this property.  In some deployments where remote delegates are scaled out many times, the bottleneck can become the aggregate deserializing CASes from the reply queue.  If the aggregate is running on a multicore machine it helps to increase the number of threads that can process the reply queue.

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