You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/10/21 21:00:59 UTC
[jira] Created: (UIMA-1632) UIMA AS service does not recover from
broker failure and subsequent restart
UIMA AS service does not recover from broker failure and subsequent restart
---------------------------------------------------------------------------
Key: UIMA-1632
URL: https://issues.apache.org/jira/browse/UIMA-1632
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Fix For: 2.3AS
When the broker dies and is subsequently restarted, the UIMA AS service recovers listeners on its input queue but it is not cleaning up its endpoints to remote delegates properly. In a request to the remote delegate, the service sends an old temp reply queue. This leads to JMS exceptions in the delegate while trying to reply to tmp destinations that no longer exist in a new broker. Fix the code to recover connection from a failed broker, clear the cache of delegate endpoints, create a new temp reply queue and listener and add a new temp reply queue to the outgoing request message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1632) UIMA AS service does not recover from
broker failure and subsequent restart
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1632.
-------------------------------
Resolution: Fixed
Fixes the recovery from a bounced broker. Creates new connection, new temp queue and listener, and invalidates connection cache.
> UIMA AS service does not recover from broker failure and subsequent restart
> ---------------------------------------------------------------------------
>
> Key: UIMA-1632
> URL: https://issues.apache.org/jira/browse/UIMA-1632
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> When the broker dies and is subsequently restarted, the UIMA AS service recovers listeners on its input queue but it is not cleaning up its endpoints to remote delegates properly. In a request to the remote delegate, the service sends an old temp reply queue. This leads to JMS exceptions in the delegate while trying to reply to tmp destinations that no longer exist in a new broker. Fix the code to recover connection from a failed broker, clear the cache of delegate endpoints, create a new temp reply queue and listener and add a new temp reply queue to the outgoing request message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.