You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2015/07/02 17:22:04 UTC

[jira] [Updated] (UIMA-4475) DUCC Job Driver (JD) initially and incorrectly shows DriverProcessFailed for JD that ends normally

     [ https://issues.apache.org/jira/browse/UIMA-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro updated UIMA-4475:
-------------------------------
    Fix Version/s:     (was: future-DUCC)
                   2.0.0-Ducc

> DUCC Job Driver (JD) initially and incorrectly shows DriverProcessFailed for JD that ends normally
> --------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4475
>                 URL: https://issues.apache.org/jira/browse/UIMA-4475
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 2.0.0-Ducc
>
>
> I did notice a bug in the WS. When a Job changes state from 
> Running to Completed, its Reason or Extraordinary Status changes to DriverProcessFailed. The reason changes to EndOfJob when a JD
> process terminates. I dont think an Agent sets the reason=DriverProcessFailed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)