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 2013/11/01 10:51:26 UTC

[jira] [Resolved] (UIMA-3365) DUCC job driver (JD) ERROR client.WorkItemListener onBeforeProcessCASHandler N/A seqNo:null casId:1602519189 java.lang.NullPointerException

     [ https://issues.apache.org/jira/browse/UIMA-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro resolved UIMA-3365.
--------------------------------

    Resolution: Fixed

JD status report returns wrong value for getWorkItemsDispatched()

> DUCC job driver (JD) ERROR client.WorkItemListener onBeforeProcessCASHandler     N/A seqNo:null casId:1602519189 java.lang.NullPointerException
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-3365
>                 URL: https://issues.apache.org/jira/browse/UIMA-3365
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 1.0-Ducc
>
>
> Job 93735.
> It seems that the first callback expected by JD for work item 659 comes.  However the second callback does not arrive within 60 seconds, so the work items is reaped.  Then, 2 seconds later the missing callback finally (and unexpectedly) arrives causing the NPE in JD.
> The Job seems to actually run to completion, but is flagged with lost work items.  This makes sense, since if the JP does get the work item it will process it.  However, the JD will begin queuing "extra" work items since it does not understand that such work items are not really lost.  This may increasingly aggravate the problem by having the JD put out to queue more work items than the present JP capacity can handle.



--
This message was sent by Atlassian JIRA
(v6.1#6144)