[jira] [Commented] (UIMA-3073) DUCC webserver (WS) shows job not completed, yet jd.out.log show all work items ended?

["Lou DeGenaro (JIRA)" <de...@uima.apache.org>]

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

Lou DeGenaro commented on UIMA-3073:
------------------------------------

A similar situation arose on the Reservation page.  Several showed WaitingForResources, yet the Reservations were actually Completed.  This was shown by a) running as shadow WS which showed the correct data and b) re-booting the actual WS likewise.

It may be the case that the last OR publication seen by WS contains the entities in question (Jobs, Reservations) with non-final status.  Later the next publication processed by the WS (presuming several OR pubs were "missing" for whatever reason) has those entities removed.

The rule should be:  if the WS notices that an entity has disappeared from the OR publication, and that entity did not have final (Completed) status, then the WS should get same form history.

> DUCC webserver (WS) shows job not completed, yet jd.out.log show all work items ended?
> --------------------------------------------------------------------------------------
>
>                 Key: UIMA-3073
>                 URL: https://issues.apache.org/jira/browse/UIMA-3073
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: future-DUCC
>
>
> It seems that all work items for job 60037 completed, by examination of jd.out.log.  Yet WS shows otherwise.
> Perhaps more logging is needed in OR to determine if correct JD publications are arriving.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)