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

["Burn Lewis (JIRA)" <ui...@incubator.apache.org>]

     [ 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-patch.txt

UIMA-955 added support for duplicate queue names if on different brokers, but it doesn't work if the service does not have that patch and uses an internal URI for its broker that is different from the external URI used by the client.  This patch adds support for old 2.2.2 services but with the (unchecked) restriction that their queue names must be unique within the client, as was the case in 2.2.2

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