Bill,
We're putting a major effort into speeding up server startup, so it
makes sense to have the information available. We don't have a good
set of criteria for what shows up in the server log at startup; I
think this qualifies more than a lot of stuff I see in the log.
Perhaps it's mostly for developers as far as being actionable. But it
gives hard data that a customer or user of Glassfish could pass back
to use, which might be helpful in understanding its performance. The
'time' command does not suffice; it includes asadmin as well as being
misleading for quick startup. The log message times things from when
main() is called; this is the code we can optimize (thanks to Byron
to speeding up the launch part).
The message is misleading currently; no mention is made of whether
it's a quick startup or not eg:
"-Dcom.sun.enterprise.server.ss.ASQuickStartup=true/false".
The difference is factor of at least 3-4X on a basic PE install.
I'll clarify that in the message.
Lloyd
On Dec 4, 2006, at 9:42 PM, Bill Shannon wrote:
> Lloyd L Chambers wrote:
>> Bill,
>> Because FINE generate an enormous amount of stuff that buries
>> anything useful. This way, it's still one message. I think
>> startup time is probably useful to system admins, too, and the
>> cost is a few more bytes in the log file.
>
> I expected that few people other than a small subset of app server
> developers would really care how long it took to start up. If in
> fact you think a large number of people will care exactly how long
> it takes to start up, include that information. But I'm curious,
> what are most people going to *do* with that information?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>