commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DAEMON-337) Docu-Bug on procrun page
Date Fri, 07 Apr 2017 15:11:42 GMT

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

Chris Thistlethwaite updated DAEMON-337:
----------------------------------------
    Reporter: Daniel H. Peger  (was: Daniel)

> Docu-Bug on procrun page
> ------------------------
>
>                 Key: DAEMON-337
>                 URL: https://issues.apache.org/jira/browse/DAEMON-337
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>            Reporter: Daniel H. Peger
>            Priority: Minor
>
> There seems to be a docu-bug on the procrun page (http://commons.apache.org/proper/commons-daemon/procrun.html):
> The description of the {{--StartMethod}} parameter states:
> {quote}
> Note: in jvm mode, the start method should not return until the stop method has been
called.
> {quote}
> But further down the page in the "Using Procrun in jvm mode" section:
> {quote}
> Note that the method handling service start should create and start a separate thread
to carry out the processing, and then return. The start and stop methods are called from different
threads.
> {quote}
> If I'm not reading this wrong, this a little conflicting.
> From my understanding the implementation of the start-method should be synchronous, that
is the first note would be correct and the second one should be adapted.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message