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 2017/06/13 17:23:01 UTC

[jira] [Comment Edited] (UIMA-5447) DUCC ducc_watcher script improvements - timestamp & unable to write state

    [ https://issues.apache.org/jira/browse/UIMA-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048055#comment-16048055 ] 

Lou DeGenaro edited comment on UIMA-5447 at 6/13/17 5:22 PM:
-------------------------------------------------------------

Set timeout of 30 seconds on http request to WS so as to minimize overlap with next ducc_watcher cron job, nominally launched at 1 minute intervals.


was (Author: lou.degenaro):
Set timeout of 12 seconds on http request to WS so as to minimize overlap with next ducc_watcher cron job, nominally launched at 1 minute intervals.

> DUCC ducc_watcher script improvements - timestamp & unable to write state
> -------------------------------------------------------------------------
>
>                 Key: UIMA-5447
>                 URL: https://issues.apache.org/jira/browse/UIMA-5447
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.1.0-Ducc
>
>
> ducc_watcher keeps its state in the filesystem.  Successive invocations rely on this state in order to eliminate duplicate e-mails.  In the event that the state can be read but not written (e.g. file system problems) more information would be helpful, specifically:
> 1. add timestamp to message text at time of generation
> 2. include "state file write failed" or similar in message text



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)