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 2015/07/27 22:29:05 UTC

[jira] [Updated] (UIMA-4540) DUCC JP does not publish final AE init stats when it completes initialization

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

Jerry Cwiklik updated UIMA-4540:
--------------------------------
    Description: 
When a JP is launched, it starts an executor which spins a thread every 20 seconds to collect AE initialization status which is published to an agent.

When all AEs initialize, a JP stops the executor and a reporting thread preventing the final update from being sent to an agent. The WS in such case is never updated and shows stale information.

Fix: modifiy JobProcessComponent.start() to force an update to an agent before stopping the executor..

  was:
When JP starts it starts an executor which spins a thread every 20 seconds to collect AE initialization status and sends an update to an agent. When all AEs initialize the, the JP stops the executor and a reporting thread preventing a final update to an agent. The WS in such case is never updated and shows stale information.
Fix: before stopping an executor force an update to the agent.


> DUCC JP does not publish final AE init stats when it completes initialization
> -----------------------------------------------------------------------------
>
>                 Key: UIMA-4540
>                 URL: https://issues.apache.org/jira/browse/UIMA-4540
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.1.0-Ducc
>
>
> When a JP is launched, it starts an executor which spins a thread every 20 seconds to collect AE initialization status which is published to an agent.
> When all AEs initialize, a JP stops the executor and a reporting thread preventing the final update from being sent to an agent. The WS in such case is never updated and shows stale information.
> Fix: modifiy JobProcessComponent.start() to force an update to an agent before stopping the executor..



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