[
https://issues.apache.org/jira/browse/UIMA-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616955#action_12616955
]
Jerry Cwiklik commented on UIMA-1124:
-------------------------------------
Although I agree that it should be possible to send a CAS to remotes (managed
by different brokers) each having an input queue with the same name, I am
questioning such idea for collocated services. No guarantee which service
receives the CAS. Such mis-configuration should be caught by dd2spring.
I am aware of the inconsistencies in the log and will address these soon. This
work needs a seperate JIRA.
> If 2 delegates use the same queue name getMeta will time out on one of them
> ---------------------------------------------------------------------------
>
> Key: UIMA-1124
> URL: https://issues.apache.org/jira/browse/UIMA-1124
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Burn Lewis
> Fix For: 2.2.2AS
>
>
> It should be possible (if unusual) to send a CAS to the same queue from
> different stages in its flow. Or at least to a queue with the same name on a
> different broker. Alternatively if we insist that aggregates must have
> unique queue names then we should enforce it. The problem may be related to
> the fact that most log messages refer to queue names instead of delegate
> keys, e.g. when key UMA_TL uses queue TopicLabellerAnnotatorQueue we get:
> UMA_TL Remote Service Registered Successfully
> Merging Typesystem From Delegate: TopicLabellerAnnotatorQueue
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
