[UIMA-5110] DUCC Job Driver (JD) erroneously logs ***** TIMEOUT *****

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.0-Ducc
• Component/s: DUCC
• Assignee: Lou DeGenaro
• Reporter: Lou DeGenaro
• Created: 15/Sep/16 20:52
• Updated: 19/Dec/16 16:27
• Resolved: 19/Dec/16 16:27

Description

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!