[ 
https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618844#action_12618844
 ] 

Marshall Schor commented on UIMA-1130:
--------------------------------------

The deployment descriptor currently has:

 <remoteAnalysisEngine key="key name"> <!-- 0 or more -->
           . . .
            <replyQueue location="[local|remote]"/><!-- optional-->

Some possibilities:
  a) if the location= is specified and is "local", give a message "local reply 
queue no longer supported"
  b) We *could* force the local option to be remote - would this be a good 
idea? or should we just give an error message and force the user to update the 
descriptor?  
  c) To support specifying tne number of concurrant consumers of the reply q, I 
propose adding an attribute to the replyQueue: "concurrantConsumers" with a 
defualt value of 1.  

I'll proceed with this design / impl with the error message if the user says 
"local", unless other voices speak up :-)


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

Reply via email to