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 2016/09/15 20:53:20 UTC
[jira] [Created] (UIMA-5110) DUCC Job Driver (JD) erroneously logs
***** TIMEOUT *****
Lou DeGenaro created UIMA-5110:
----------------------------------
Summary: DUCC Job Driver (JD) erroneously logs ***** TIMEOUT *****
Key: UIMA-5110
URL: https://issues.apache.org/jira/browse/UIMA-5110
Project: UIMA
Issue Type: Bug
Components: DUCC
Reporter: Lou DeGenaro
Assignee: Lou DeGenaro
Fix For: 2.2.0-Ducc
In the JD log we see:
14 Sep 2016 10:41:29,157 ERROR JD.err - T[34] record seqNo=2 ***** TIMEOUT *****
[B@e9a57948
But this log entry is not correct. The real problem is that the JD tried to convert the Exception object that occurred in "user space" into a string, but that fails and the JD then makes the wrong assumption that a timeout must have occurred because it finds value of null for the stringified Exception...wrong!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)