uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-3319) DUCC Agent Reports Wrong State For APs and JPs
Date Fri, 25 Oct 2013 14:16:31 GMT

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

Lou DeGenaro commented on UIMA-3319:

Improve webserver (WS) LinuxSignals utility to comprise both lower=128 and upper=128+32 bounds
for isSignal determination relative to process exit code.

Code delivered.

> DUCC Agent Reports Wrong State For APs and JPs
> ----------------------------------------------
>                 Key: UIMA-3319
>                 URL: https://issues.apache.org/jira/browse/UIMA-3319
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Lou DeGenaro
>             Fix For: 1.0-Ducc
> When a process exits normally or terminates due to a kill not initiated by DUCC, the
Agent marks the process as Failed with Reason Croaked. The agent has no way to determine if
the process exited gracefully or due to an error. The return code from the process can be
interrogated to see if the process was killed due to a signal. In such case, the high bit
in the return code will be set. When the process exits not due to a signal is where the problem
exists. No way of knowing why that happened. This is user code and as such cannot be relied
> Modify the agent to change state of the process to Stopped instead of Failed. If the
process was killed by an agent the reason should be KilledByDucc both for APs and JPs. If
the process exited on its own, the reason should be Other.

This message was sent by Atlassian JIRA

View raw message