[
https://issues.apache.org/jira/browse/UIMA-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-3319:
--------------------------------
Description:
When an AP 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 upon.
Modify the agent to change state of the process to Stopped instead of Failed.
If the AP was killed by an agent the reason should be KilledByDucc. If the
process exited on its own, the reason should be Other.
was:
When an AP 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 upon.
Modify the agent to change state of the process to Stopped instead of Failed.
If the AP was killed by an agent the reason should be KilledByDuck. If the
process exited on its own, the reason should be Other.
> DUCC Agent Reports Wrong State For APs
> --------------------------------------
>
> Key: UIMA-3319
> URL: https://issues.apache.org/jira/browse/UIMA-3319
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 1.0-Ducc
>
>
> When an AP 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 upon.
> Modify the agent to change state of the process to Stopped instead of Failed.
> If the AP was killed by an agent the reason should be KilledByDucc. If the
> process exited on its own, the reason should be Other.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
