[
https://issues.apache.org/jira/browse/UIMA-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634293#action_12634293
]
Marshall Schor commented on UIMA-1140:
--------------------------------------
1) I found that dd2spring was generating a message handler chain for reply
queues that was including the handlers for the out-going getMeta and process
calls - I removed these.
2) after some discussion with Jerry, I changed the logic in dd2spring for
message handler chains, input channels, and listeners as follows:
* Top level has "input" versions of these; co-located inner components do not
* If any delegates are remote, then those remotes have individual instances of
input channels and listeners for "return/replies", but share the message
handler chain for returning messages.
** If no delegate is remote, then no "return" input channles, listeners, or
message handler chains are made.
* Doing #11 above - change references to this output channel to null (actually,
remove the <property ...> element referring to it
> 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.
