uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1298) A shared remote CM hangs when one of its clients runs out of memory
Date Fri, 10 Apr 2009 17:57:14 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697886#action_12697886
] 

Jerry Cwiklik commented on UIMA-1298:
-------------------------------------

This indicates that the client that crashed did not send requests to free CASes. Most likely
all CM CASes have been drained and the service is hung on an empty pool. How do you suggest
to fix this? Using a timer to time freeCas requests seems difficult to get right. 

> 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
>            Reporter: Burn Lewis
>            Priority: Minor
>             Fix For: 2.3S
>
>
> 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.


Mime
View raw message