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 2016/03/27 17:17:25 UTC
[jira] [Created] (UIMA-4878) UIMA-DUCC: Agent not killing a child
process if it fails to stop after SIGTERM
Jerry Cwiklik created UIMA-4878:
-----------------------------------
Summary: UIMA-DUCC: Agent not killing a child process if it fails to stop after SIGTERM
Key: UIMA-4878
URL: https://issues.apache.org/jira/browse/UIMA-4878
Project: UIMA
Issue Type: Bug
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
Fix For: 2.1.0-Ducc
Agent is not killing a process which fails to exit after SIGTERM is sent. When kill -15 is issued, an agent immediately sets the process state to Stopped even though the process may still be running. If a process is in Stopped state, an agent does not start a kill timer for it which leads to a process lingering on a node. The kill timer waits a configurable amount of time and when it pops, it sends SIGKILL signal to a process if its still running.
Modify code to change process state to Stopped when the process actually terminates. The agent has a handle to a process and calls its waitFor() which blocks until the process exits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)