[jira] [Updated] (UIMA-3707) DUCC SM should mark custom pingers so they're more easily reaped.

["Jim Challenger (JIRA)" <de...@uima.apache.org>]

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

Jim Challenger updated UIMA-3707:
---------------------------------

    Affects Version/s: 1.1.0-Ducc
        Fix Version/s: 1.1.0-Ducc

The update sets -DSM_MONITOR as the first jvm parameter so it is easy to find using ps.

> DUCC SM should mark custom pingers so they're more easily reaped.
> -----------------------------------------------------------------
>
>                 Key: UIMA-3707
>                 URL: https://issues.apache.org/jira/browse/UIMA-3707
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>            Priority: Minor
>             Fix For: 1.1.0-Ducc
>
>
> If the Service Manager is killed-with-prejudice it can leave CUSTOM pingers alive and orphaned (children of init).
> SM should clearly mark these processes so cleanup procedures can easily find them and reap them as part of system startup.  The proposed mechanism is to set a -Dmarker as a no-op system property to ServicePingMain that is easily discovered using ps.  Startup scripting (and check_ducc) will look for these processes and kill them prior to starting SM.
> As well SM should implement a shutdown hook that attempts to stop these pingers if it is stopped with only-a-little-prejudice.



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