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)" <de...@uima.apache.org> on 2012/10/11 21:21:02 UTC
[jira] [Created] (UIMA-2477) UIMA-AS Not Handling Late Replies
Correctly
Jerry Cwiklik created UIMA-2477:
-----------------------------------
Summary: UIMA-AS Not Handling Late Replies Correctly
Key: UIMA-2477
URL: https://issues.apache.org/jira/browse/UIMA-2477
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
Fix For: 2.4.0AS
When UIMA-AS aggregate receives late (previously timed out) reply from a remote delegate it tries to drop related Flow object from a FC and subsequently removes a CAS from its cache. This is wrong. Its up to the FC to decide what to do with a timed out CAS. In a scenario when the FC continues with a timed out CAS, current code may cause NPEs in the AE and an unexpected shutdown of the service if action=terminate on Process error. The code should be changed to ignore out-of-band CASes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (UIMA-2477) UIMA-AS Not Handling Late Replies
Correctly
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-2477.
-------------------------------
Resolution: Fixed
Modified code to ignore out of band CASes
> UIMA-AS Not Handling Late Replies Correctly
> -------------------------------------------
>
> Key: UIMA-2477
> URL: https://issues.apache.org/jira/browse/UIMA-2477
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.0AS
>
>
> When UIMA-AS aggregate receives late (previously timed out) reply from a remote delegate it tries to drop related Flow object from a FC and subsequently removes a CAS from its cache. This is wrong. Its up to the FC to decide what to do with a timed out CAS. In a scenario when the FC continues with a timed out CAS, current code may cause NPEs in the AE and an unexpected shutdown of the service if action=terminate on Process error. The code should be changed to ignore out-of-band CASes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira