You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2006/05/19 02:10:08 UTC
[jira] Closed: (GERONIMO-1997) Not possible to account for startup
time in --long startup output due to configurations showing 0s
[ http://issues.apache.org/jira/browse/GERONIMO-1997?page=all ]
John Sisson closed GERONIMO-1997:
---------------------------------
Resolution: Fixed
Fixed in http://svn.apache.org/viewcvs?rev=405446&view=rev
> Not possible to account for startup time in --long startup output due to configurations showing 0s
> --------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-1997
> URL: http://issues.apache.org/jira/browse/GERONIMO-1997
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: startup/shutdown
> Versions: 1.0, 1.1
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Trivial
> Fix For: 1.1
>
> If you look at the --long startup output you will see that there are a number of configurations with a startup time of 0 seconds. These in fact could have been a fraction under a second, but it is displayed as 0. If you add up the startup times below it will add up to 12 seconds, yet the total startup time was 16 seconds. Four seconds were not accounted for in the display.
> The startup times should also display hundreths of seconds.
> -------------------------------------------------
> C:\test>geronimo-1.1-SNAPSHOT\bin\geronimo.bat run --long
> Using GERONIMO_BASE: C:\test\geronimo-1.1-SNAPSHOT
> Using GERONIMO_HOME: C:\test\geronimo-1.1-SNAPSHOT
> Using GERONIMO_TMPDIR: C:\test\geronimo-1.1-SNAPSHOT\var\temp
> Using JRE_HOME: C:\j2sdk1.4.2_10
> Booting Geronimo Kernel (in Java 1.4.2_10)...
> Configuration 1/20 geronimo/rmi-naming/1.1-SNAPSHOT/car started in 0s
> Configuration 2/20 geronimo/j2ee-server/1.1-SNAPSHOT/car started in 1s
> Configuration 3/20 geronimo/j2ee-security/1.1-SNAPSHOT/car started in 1s
> Configuration 4/20 geronimo/axis/1.1-SNAPSHOT/car started in 0s
> Configuration 5/20 geronimo/openejb/1.1-SNAPSHOT/car started in 0s
> Configuration 6/20 geronimo/system-database/1.1-SNAPSHOT/car started in 2s
> Configuration 7/20 geronimo/activemq-broker/1.1-SNAPSHOT/car started in 1s
> Configuration 8/20 geronimo/activemq/1.1-SNAPSHOT/car started in 1s
> Configuration 9/20 geronimo/tomcat/1.1-SNAPSHOT/car started in 3s
> Configuration 10/20 geronimo/geronimo-gbean-deployer/1.1-SNAPSHOT/car started in 1s
> Configuration 11/20 geronimo/j2ee-deployer/1.1-SNAPSHOT/car started in 0s
> Configuration 12/20 geronimo/openejb-deployer/1.1-SNAPSHOT/car started in 0s
> Configuration 13/20 geronimo/client-deployer/1.1-SNAPSHOT/car started in 0s
> Configuration 14/20 geronimo/axis-deployer/1.1-SNAPSHOT/car started in 0s
> Configuration 15/20 geronimo/sharedlib/1.1-SNAPSHOT/car started in 0s
> Configuration 16/20 geronimo/tomcat-deployer/1.1-SNAPSHOT/car started in 0s
> Configuration 17/20 geronimo/welcome-tomcat/1.1-SNAPSHOT/car started in 0s
> Configuration 18/20 geronimo/webconsole-tomcat/1.1-SNAPSHOT/car started in 2s
> Configuration 19/20 geronimo/remote-deploy-tomcat/1.1-SNAPSHOT/car started in 0s
> Configuration 20/20 geronimo/hot-deployer/1.1-SNAPSHOT/car started in 0s
> Startup completed in 16 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira