[ http://issues.apache.org/jira/browse/GERONIMO-1867?page=all ]
John Sisson closed GERONIMO-1867:
---------------------------------
Resolution: Fixed
> Startup output from --long badly formatted (regression from 1.0)
> ----------------------------------------------------------------
>
> Key: GERONIMO-1867
> URL: http://issues.apache.org/jira/browse/GERONIMO-1867
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: startup/shutdown
> Versions: 1.1
> Reporter: John Sisson
> Assignee: John Sisson
> Fix For: 1.1
>
> The n/total count for each configuration is displayed in the wrong position
> on the line. ( IIRC djencks said he changed the startup output from what was
> in 1.0 so you could see which configuration is currently starting.
> Previously in 1.0 a line was only output when a configuration had started ).
> For example:
> Configuration geronimo/rmi-naming/1.1-SNAPSHOT/car started in 1/16 0s
> needs to be changed to display :
> Configuration 1/16 geronimo/rmi-naming/1.1-SNAPSHOT/car started in 0s
> Also it would look better if the startup times are aligned for easier reading
> and comparison. This should be possible from memory as we should be able to
> calculate the longest configuration name before we start.
> Here is an example of the current output:
> $./geronimo.sh run --long
> Using GERONIMO_BASE:
> /home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT
> Using GERONIMO_HOME:
> /home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT
> Using GERONIMO_TMPDIR:
> /home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/var/temp
> Using JRE_HOME: /usr/j2se
> Booting Geronimo Kernel (in Java 1.4.2_10)...
> Configuration geronimo/rmi-naming/1.1-SNAPSHOT/car started in 1/16 0s
> Configuration geronimo/j2ee-server/1.1-SNAPSHOT/car started in 2/16 2s
> Configuration geronimo/j2ee-security/1.1-SNAPSHOT/car started in 3/16 1s
> Configuration geronimo/system-database/1.1-SNAPSHOT/car started in 4/16 4s
> Configuration geronimo/activemq-broker/1.1-SNAPSHOT/car started in 5/16 2s
> Configuration geronimo/activemq/1.1-SNAPSHOT/car started in 6/16 0s
> Configuration geronimo/tomcat/1.1-SNAPSHOT/car started in 7/16 4s
> Configuration geronimo/geronimo-gbean-deployer/1.1-SNAPSHOT/car started in
> 8/16 1s
> Configuration geronimo/j2ee-deployer/1.1-SNAPSHOT/car started in 9/16 1s
> Configuration geronimo/tomcat-deployer/1.1-SNAPSHOT/car started in 10/16 0s
> Configuration geronimo/welcome-tomcat/1.1-SNAPSHOT/car started in 11/16 0s
> Configuration geronimo/webconsole-tomcat/1.1-SNAPSHOT/car started in 12/16
> 2s
> Configuration geronimo/jmxdebug-tomcat/1.1-SNAPSHOT/car started in 13/16 1s
> Configuration geronimo/remote-deploy-tomcat/1.1-SNAPSHOT/car started in 14/16
> 0s
> Configuration geronimo/hot-deployer/1.1-SNAPSHOT/car started in 15/16 1s
> Configuration geronimo/sharedlib/1.1-SNAPSHOT/car started in 16/16 0s
> Startup completed in 25 seconds
> <SNIP>
> After the fix, the output now looks like the following (note that the
> configuration names are padded to the length of the longest configuration
> name so the startup times line up):
> 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 2s
> 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 1s
> 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
> <SNIP>
--
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
