[
https://issues.apache.org/jira/browse/UIMA-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-937:
-------------------------------
Attachment: uimaj-as-core-UIMA-937-patch.txt
uimaj-as-activemq-UIMA-937-patch.txt
Fixed the JmsEndpointConnection_impl to fetch the right Broker URL when
replying to temp queues. Added new testcase to test tunnelling over HTTP from a
UIMA AS Client to a remote UIMA AS Aggregate.
> UIMA AS service fetches a wrong Broker URL from the controller on replies
> -------------------------------------------------------------------------
>
> Key: UIMA-937
> URL: https://issues.apache.org/jira/browse/UIMA-937
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.2.2S
>
> Attachments: uimaj-as-activemq-UIMA-937-patch.txt,
> uimaj-as-core-UIMA-937-patch.txt
>
>
> When trying to reply to a temp queue, the JmsEndpointConnection_impl object
> fetches a wrong broker URL from the controller. Temp queues are managed by
> the same broker as the service input queue, so that the replies must go to a
> temp queue managed by the same broker. What seems to be happening is that
> the JmsEndpointConnection_impl object fetches an Internal Broker URL
> instead. Replies are never sent to the client. This problem happens when a
> client tunnels messages over HTTP to a remote Aggregate AS Service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
