You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org> on 2009/12/15 11:17:18 UTC
[jira] Created: (UIMA-1706) UIMA AS Camel driver should handle
broker connection lost correctly
UIMA AS Camel driver should handle broker connection lost correctly
-------------------------------------------------------------------
Key: UIMA-1706
URL: https://issues.apache.org/jira/browse/UIMA-1706
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.3AS
Reporter: Jörn Kottmann
Assignee: Jörn Kottmann
Fix For: 2.3AS
In the case of a broker connection lost the system might hang, because it is waiting for outstanding CASes which will
never return, because after reconnecting to the broker the old temp reply queue cannot be accessed anymore.
When the system receives a BrokerConnectionException all outstanding CASes should be reported as failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1706) UIMA AS Camel driver should handle
broker connection lost correctly
Posted by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörn Kottmann closed UIMA-1706.
-------------------------------
Resolution: Fixed
> UIMA AS Camel driver should handle broker connection lost correctly
> -------------------------------------------------------------------
>
> Key: UIMA-1706
> URL: https://issues.apache.org/jira/browse/UIMA-1706
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jörn Kottmann
> Assignee: Jörn Kottmann
> Fix For: 2.3AS
>
>
> In the case of a broker connection lost the system might hang, because it is waiting for outstanding CASes which will
> never return, because after reconnecting to the broker the old temp reply queue cannot be accessed anymore.
> When the system receives a BrokerConnectionException all outstanding CASes should be reported as failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.