[
https://issues.apache.org/jira/browse/UIMA-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1298.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.3.1AS
Modified to stop CM from producing new CASes if a send() fails while trying to
deliver a CAS to a client. All outstanding CASes (those that have been sent to
a client but not explicitly freed), will be released. The parent CAS will be
unlocked and subsequently releases to the service's Cas Pool. This only fix
addresses a scenario where the client's reply queue is removed.
> 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
> Fix For: 2.3.1AS
>
>
> 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.
