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 2014/07/02 16:32:25 UTC
[jira] [Commented] (UIMA-3921) When a JD fails to start
(e.g.classpath error) it marks the job as complete
[ https://issues.apache.org/jira/browse/UIMA-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049956#comment-14049956 ]
Lou DeGenaro commented on UIMA-3921:
------------------------------------
I created a version of this problem by hacking resources/jobclasspath.properties and removing a required jar repository, in particular ${DUCC_HOME}/lib/apache-commons-lang/*:\
Observed was the Job stuck in state WaitingForDriver. The reality was that the Job Driver worker thread failed with an error and exited.
> When a JD fails to start (e.g.classpath error) it marks the job as complete
> ---------------------------------------------------------------------------
>
> Key: UIMA-3921
> URL: https://issues.apache.org/jira/browse/UIMA-3921
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Burn Lewis
> Assignee: Lou DeGenaro
> Priority: Minor
> Fix For: future-DUCC
>
>
> The agent reports that it has an exit code of 1 ... perhaps it could determine that the process never started and give a more serious error.
--
This message was sent by Atlassian JIRA
(v6.2#6252)