[jira] [Closed] (UIMA-2105) UIMA AS Aggregate Not Handling Broker Restart

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

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

Jerry Cwiklik closed UIMA-2105.
-------------------------------

    Resolution: Fixed

Modified JmsOutputChannel to create a new temp reply queue and a listener for remote delegate after broker restart. 

> UIMA AS Aggregate Not Handling Broker Restart 
> ----------------------------------------------
>
>                 Key: UIMA-2105
>                 URL: https://issues.apache.org/jira/browse/UIMA-2105
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3.2AS
>
>
> UIMA AS aggregate with remote delegate is not recovering correctly when a broker is stopped and subsequently restarted. In this scenario, both the aggregate and the delegate reconnect to the new broker, which is expected. The problem is that the aggregate is not creating a new temp queue and corresponding listener for the remote delegate. The aggregate actually creates the temp queue and a listener if and only if maxRetries>0 in the delegate's error handling configuration. The recovery should be done regardless of the this setting. After broker restart, the subsequent CAS coming in to the aggregate should force creation of a temp reply queue and a new listener on that queue before the CAS is sent to a remote delegate.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira