Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.212.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=tYpwPrxDxoAd9BHKpEz2RP1V/UlbosyMaqTQYMZmNRa1d+l6bB9ijBzG1hktMvBQ2w
         C98m1RB5ln6kqzmyax+foP8Em6WY6Qk2nJXug3EGa6xm2+/C2oVagleSrxHnmN1EMeP2
         WYgQuQ3oRvyMDKRU3yroqhU86phFWj+MTGUAs=
MIME-Version: 1.0
In-Reply-To: <4DF9DB07.6010708@pidster.com>
References: <BANLkTikBib_1E5c-p3w3QwWnU_uxWju5Mg@mail.gmail.com>
	<4DF9DB07.6010708@pidster.com>
Date: Thu, 16 Jun 2011 12:04:18 +0100
Message-ID: <BANLkTi=+Yej68giLvE-R5iyQtR0HpWbGEg@mail.gmail.com>
Subject: Re: Feature request: "fullstart" command
From: sebb <sebbaz@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On 16 June 2011 11:29, Pid <pid@pidster.com> wrote:
> On 15/06/2011 21:00, Francis GALIEGUE wrote:
>> Tomcat has many abilities to deploy applications at run time (war,
>> tree, context, you name it). However, when used in production, these
>> abilities are used cautiously, if they are used at all.
>>
>> In many scenarios, Tomcat just starts, spends its life, and stops,
>> with a defined set of webapps, and has no automatic deployment
>> capabilities configured in at all. But the builtin startup scripts,
>> and in fact, the Java code itself, lack at least two critical inputs
>> for such scenarios:
>>
>> * Bootstrap will return (and therefore the startup scripts too) before
>> webapps configured at startup time are deployed, and while
>> bootstrapping is fast, deploying applications at startup can be very
>> long;
>> * even with a hackish way (watch the log file to account for complete
>> server startup) in order to wait for webapps to be deployed, there is
>> no status about these deployments at all (has this and that webapp
>> been deployed successfully?).
>
> An application might report that it's started, even it hasn't finished
> initialising.
>
>
>> Proposal: implement a fullstart command to Bootstrap which:
>>
>> * does NOT return until ALL webapps configured at start time are
>> (attempted to be) deployed;
>> * exits with a positive error code representing the number of webapps
>> NOT correctly deployed (or 1 - I don't care as long as it's not 0, but
>> please not -1, think WIFSIGNALED()).
>
> 'fullstart' is an odd name, people might start using it thinking that
> 'start' did not fully start the server.
>
> Returning an exit code which describes the number of apps successfully
> started isn't much use unless you (or the init script) know the number
> of apps configured.
>

And it may cause problems on some OSes which don't use unix-style exit codes.
For example, OpenVMS uses the low order 3 bits of a process exit code
as a severity indicator, and odd is success, even is failure.
[IThe JVM automatically converts exit 0 to exit 1 to compensate, but
cannot deal with all exit codes].

> p
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org