uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burn Lewis (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Closed: (UIMA-1124) If 2 delegates use the same queue name getMeta will time out on one of them
Date Fri, 05 Sep 2008 22:24:44 GMT

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

Burn Lewis closed UIMA-1124.
----------------------------

    Resolution: Duplicate

This is a duplicate of UIMA-955

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


Mime
View raw message