Burn Lewis created UIMA-4321:
--------------------------------
Summary: DUCC should nt retry JPs forever when
Key: UIMA-4321
URL: https://issues.apache.org/jira/browse/UIMA-4321
Project: UIMA
Issue Type: Bug
Components: DUCC
Affects Versions: 2.0.0-Ducc
Reporter: Burn Lewis
Assignee: Jerry Cwiklik
Priority: Blocker
Job 235131 had a large string of JPs fail (when the JD OOM'd) with:
HttpWorkerThread.run() I/O exception
(org.apache.commons.httpclient.NoHttpResponseException) caught when processing
request: The server 192.168.3.77 failed to respond
For the short-term we should count this as a Croak (i.e. an unexpected
termination that DUCC didn't request), even though it is not caused by user
error, so that the users's process_failures_limit can eventually end the job.
Perhaps we need a "framework_failures_limit" in ducc.properties for errors
caught in the ducc-side JP code as opposed to errors caught in user code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
