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 2014/04/30 20:32:15 UTC

[jira] [Closed] (UIMA-3580) DUCC Agent sends STOP instead of QUIESCE to a running process

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

Jerry Cwiklik closed UIMA-3580.
-------------------------------

    Resolution: Fixed

Assigned Fix Version

> DUCC Agent sends STOP instead of QUIESCE to a running process
> -------------------------------------------------------------
>
>                 Key: UIMA-3580
>                 URL: https://issues.apache.org/jira/browse/UIMA-3580
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>    Affects Versions: 1.0.0-Ducc
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 1.1.0-Ducc
>
>
> On process pre-emption (or explicit service stop), the Agent sends a Stop request to a JP or Service instead of Quiesce. The process receiving such request, stops all listeners on the input queue and also stops the output channel preventing any replies from getting back to the client (JD). 
> The above may also explain intermittent problems with GetMeta timing out. It looks like GetMeta request comes in, the service receives Stop request and immediately proceeds to stop the output channel preventing the reply. The window is very small but its possible cause of the timeout.
> If a process is killed via SIGTERM, the registered ShutdownHook correctly initiates quiesce.



--
This message was sent by Atlassian JIRA
(v6.2#6252)