commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <>
Subject [jira] [Resolved] (DAEMON-309) Documentation for start method in JVM mode is conflicting
Date Fri, 20 Oct 2017 18:59:00 GMT


Mark Thomas resolved DAEMON-309.
       Resolution: Fixed
    Fix Version/s: 1.1

Thanks for the report.

> Documentation for start method in JVM mode is conflicting
> ---------------------------------------------------------
>                 Key: DAEMON-309
>                 URL:
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>            Reporter: Joachim Sauer
>            Priority: Minor
>              Labels: doc, documentaion
>             Fix For: 1.1
> The documentation for how the start method should act in JVM mode is conflicting (
> 1. In the documentation of the StartMethod parameter there's this text:
> {quote}
> Note: in jvm mode, the start method should not return until the stop method has been
> {quote}
> 2. The second-to-last sentence in the section "Using Procrun in jvm mode" reads:
> {quote}
> Note that the method handling service start should create and start a separate thread
to carry out the processing, and then return.
> {quote}
> According to my reading those two sentences say pretty much the opposite of each other
and observation shows that #1 is the correct one (i.e. the service is assumed to have stopped
when the start method returns).
> Generally speaking, JVM mode is pretty under-documented (in my opinion). That can easily
be verified by the fact that very popular documentation exists outside the procrun/commons
daemon project, as a blog post:
> A simple end-to-end example showing a similar setup as that blog post would be good.

This message was sent by Atlassian JIRA

View raw message