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 2014/04/30 19:36:14 UTC
[jira] [Updated] (UIMA-3746) DUCC Agent not killing processes whose
state=Stopping
[ https://issues.apache.org/jira/browse/UIMA-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-3746:
--------------------------------
Affects Version/s: 1.0.0-Ducc
Fix Version/s: (was: 1.0.0-Ducc)
1.1.0-Ducc
> DUCC Agent not killing processes whose state=Stopping
> -----------------------------------------------------
>
> Key: UIMA-3746
> URL: https://issues.apache.org/jira/browse/UIMA-3746
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Affects Versions: 1.0.0-Ducc
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 1.1.0-Ducc
>
>
> Looks like an agent is not killing processes that show deallocated=true and state=Stopping. Its been observed that a process (JP) can hang while writing to a log due to quota problem. The agent seems to be getting a notification from the service wrapper that the process is stopping and changes its internal state.
> On subsequent OR publish, the process is deallocated but due to a bug it is never killed. Modify isAlive() in NodeAgent to include check if the process is in Stopping state when deciding whether to kill the process.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)