[UIMA-4878] UIMA-DUCC: Agent not killing a child process if it fails to stop after SIGTERM

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0-Ducc
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 27/Mar/16 15:16
• Updated: 27/Mar/16 19:10
• Resolved: 27/Mar/16 19:10

Description

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.