You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2018/10/05 17:27:00 UTC

[jira] [Closed] (UIMA-5885) UIMA-DUCC The JP not waiting if JD has no work

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

Jerry Cwiklik closed UIMA-5885.
-------------------------------
    Resolution: Fixed

When JD has no more tasks, the protocol handler should wait for awhile and try again. 

> UIMA-DUCC The JP not waiting if JD has no work
> ----------------------------------------------
>
>                 Key: UIMA-5885
>                 URL: https://issues.apache.org/jira/browse/UIMA-5885
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: 2.2.3-Ducc
>
>
> When the JD has no more work to give, the JP thread (only one) should wait for awhile and try again until work is available. This used to work until recent refactoring was done to support pull service JPs. 
> By default the JP will block for 60 secs before trying again. If the service receives SIGTERM while its retry thread is waiting, such thread should be interrupted so that the service can stop. There is no need to wait until the timer (60s) expires.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)