[
https://issues.apache.org/jira/browse/UIMA-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965306#action_12965306
]
Jerry Cwiklik commented on UIMA-1298:
-------------------------------------
Changing scope of the problem to a scenario where the client of the CM
terminates abruptly. In this case, detect the failure while sending produced
(child) CAS to the client and force release of ALL outstanding CASes. Also,
since the client is no longer reachable the CM should be stopped and the input
CAS released as well. The CasIterator.release() should be called to stop the CM.
Solving the hung CM client is more difficult. Using timer to release CASes is
error prone since there is no way to easily determine what the timeout should
be.
> A shared remote CM hangs when one of its clients runs out of memory
> --------------------------------------------------------------------
>
> Key: UIMA-1298
> URL: https://issues.apache.org/jira/browse/UIMA-1298
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Burn Lewis
> Assignee: Jerry Cwiklik
> Priority: Minor
>
> Twice I observed that when one client aggregate of a shared remote CM crashed
> with an out-of-memory exception the service stopped responding to the other
> client's requests. No errors found in the service log. The client was not
> using the service at the time of the crash. Requests stacked up on the input
> queue ... almost as if the service was blocked on an empty pool, or ...?
> Killing a client (cntl-C) did not cause the hang. Weird!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
