[jira] Issue Comment Edited: (UIMA-1140) Embedded broker should be eliminated

["Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>]

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

cwiklik edited comment on UIMA-1140 at 9/24/08 9:20 AM:
--------------------------------------------------------------

Provided an alternate mechanism for messaging between colocated Uima As services. Instead of using jms based queues the internal messaging is done via java queues. The new messaging implementation uses java's ThreadPoolExecutor framework which provides necessary synchronization and threading. Each Uima As service uses a new UimaDispatcher component to send outbound messages and a UimaListener component for receiving incoming messages. Each incoming message is processed in a separate thread provided by the ThreadPoolExecutor. The number of threads used by the ThreadPoolExecutor depends on the value of the "inputQueueScaleout" attribute for  incoming messages  and the "internalReplyQueueScaleout" attribute for outgoing messages. Both of these attributes are configured in the deployment descriptor. 

*******************************************************************************************************************************
NOTE: The default messaging mechanism is *still* JMS using internal Broker. To enable java queue's for internal messaging use -DUseVmTransport=true system property. 
*******************************************************************************************************************************

Fixed Uima As controller code to enable support for colocated Aggregate Cas Multiplier.

Merged Delta Cas changes

Added new 2 testcases 

Added new API to the testcase base code to enable a testcase to pass exceptions it wants to ignore. This prevents the Exceptions from being printed on the stdout. 



      was (Author: cwiklik):
    Provided an alternate mechanism for messaging between colocated Uima As services. Instead of using jms based queues the internal messaging is done via java queues. The new messaging implementation uses java's TaskExecutor framework which provides necessary synchronization and threading. Each Uima As service uses a new UimaDispatcher component to send outbound messages and a UimaListener component for receiving incoming messages. Each incoming message is processed in a separate thread provided by the TaskExecutor. The number of threads used by the TaskExecutor depends on the value of the "inputQueueScaleout" attribute for  incoming messages  and the "internalReplyQueueScaleout" attribute for outgoing messages. Both of these attributes are configured in the deployment descriptor. 

*******************************************************************************************************************************
NOTE: The default messaging mechanism is *still* JMS using internal Broker. To enable java queue's for internal messaging use -DUseVmTransport=true system property. 
*******************************************************************************************************************************

Fixed Uima As controller code to enable support for colocated Aggregate Cas Multiplier.

Merged Delta Cas changes

Added new 2 testcases 

Added new API to the testcase base code to enable a testcase to pass exceptions it wants to ignore. This prevents the Exceptions from being printed on the stdout. 


  
> Embedded broker should be eliminated
> ------------------------------------
>
>                 Key: UIMA-1140
>                 URL: https://issues.apache.org/jira/browse/UIMA-1140
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>            Assignee: Marshall Schor
>         Attachments: uimaj-as-activemq-UIMA-1140-patch.txt, uimaj-as-core-UIMA-1140-patch.txt, uimaj-as-jms-UIMA-1140-patch.txt
>
>
> When an async aggregate is deployed, the request/reply queues for colocated delegates use an embedded broker. After UIMA-1130 is complete, all reply queues for remote delegates will be located on the same external broker hosting the delegate's request queue. At that point the function of the colocated broker can be replace with simple Java queues.

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