You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <ui...@incubator.apache.org> on 2008/11/06 19:50:44 UTC

[jira] Updated: (UIMA-1166) Getmeta replies from some remote delegates are ignored, causing a timeout

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

Burn Lewis updated UIMA-1166:
-----------------------------

    Attachment: UIMA-1166-2.patch

This patch replaces the first ... fixes one more case and is against latest code.

> Getmeta replies from some remote delegates are ignored, causing a timeout
> -------------------------------------------------------------------------
>
>                 Key: UIMA-1166
>                 URL: https://issues.apache.org/jira/browse/UIMA-1166
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>         Attachments: UIMA-1166-2.patch, UIMA-1166-patch.txt
>
>
> The reply is falsely discarded:
> 9/4/08 3:15:05 PM - 22: org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.mergeTypeSystem: INFO: Controller: IODBurnTest Received Metadata From an Invalid (Possibly Disabled) Delegate: TopicLabellerAnnotatorQueue
> The recent change to support duplicate queue names on different brokers checks the broker name returned in the reply against the broker the request was sent to.  But the service returns the name it uses for the broker, e.g. tcp://localhost:61616, and not the external name of the broker.

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