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/09/18 00:29:00 UTC

[jira] [Closed] (UIMA-5640) UIMA-DUCC: JP/Service wrapper should not sleep when Work Item is not available

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

Jerry Cwiklik closed UIMA-5640.
-------------------------------
    Resolution: Duplicate

Duplicate of https://issues.apache.org/jira/browse/UIMA-5866 and https://issues.apache.org/jira/browse/UIMA-5756. The UIMA-5866 adds support for waiting on the service side when a client is a JD. The UIMA-5756 implements no wait strategy when a client is not a JD.

> UIMA-DUCC: JP/Service wrapper should not sleep when Work Item is not available
> ------------------------------------------------------------------------------
>
>                 Key: UIMA-5640
>                 URL: https://issues.apache.org/jira/browse/UIMA-5640
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: 2.2.3-Ducc
>
>
> Currently when JD/Protocol Handler runs out of work it returns null back in response to GET. In this case, the service wrapper sleeps for a fixed amount of time and tries again. The sleeping should be done in the client (JD/Protocol Handler) to reduce latency. Instead of waiting for a fixed amount of time, the client code can use notification/interrupt to wake up a sleeping GET thread when a new work items becomes available. The service wrapper will block in http get request until a reply comes or the get request times out. On timeout, the service will immediately call the client (JD/Protocol Handler).  



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