You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2011/07/15 00:35:59 UTC
[jira] [Created] (GERONIMO-6077) Display usage information after
server startup?
Display usage information after server startup?
-----------------------------------------------
Key: GERONIMO-6077
URL: https://issues.apache.org/jira/browse/GERONIMO-6077
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Reporter: Kevan Miller
The usage information:
{code}
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Geronimo.
{code}
Would be better displayed after a server startup is complete. Also, the command prompt (i.e. 'geronimo>') is not visible after the server has been started. So, it's not apparent to new users that they can enter a command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6077) Display usage information after
server startup?
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088554#comment-13088554 ]
Rex Wang commented on GERONIMO-6077:
------------------------------------
The bundle org.apache.karaf.shell.console provide this prompt.
Currently, we include it in the startup.properties and set the start-level 30. I tried a work around to hard code in framework launcher so that the bundle won't be started when we boot karaf. But after karaf started, the geronimo server boots all the modules and seems when the org.apache.geronimo.configs/hot-deployer/3.0-SNAPSHOT/car start, it will start all its dependenies which include karaf.shell.console. This results as following, which print the geronimo in the middles of the list... Currently, geronimo is not that good integrated with osgi life cycle, so before we smooth away that, it looks like hard to resolve this problem...
-----------------------------------------------------------------------------------
D:\_g\_tr\assemblies\geronimo-tomcat7-javaee6\target\assembly\bin>geronimo run -c -l
Using GERONIMO_HOME: D:\_g\_tr\assemblies\geronimo-tomcat7-javaee6\target\assembly
Using GERONIMO_TMPDIR: var\temp
Using JRE_HOME: D:\DevJava\Java\jdk1.6.0_21\jre
Booting Geronimo Kernel (in Java 1.6.0_21)...
Module 1/63 org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car started in .000s
Module 2/63 org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car started in .156s
Module 3/63 org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car started in .281s
Module 4/63 org.apache.geronimo.framework/j2ee-security/3.0-SNAPSHOT/car started in .235s
Module 5/63 org.apache.geronimo.framework/server-security-config/3.0-SNAPSHOT/car started in .015s
Module 6/63 org.apache.geronimo.framework/bundle-recorder/3.0-SNAPSHOT/car started in .000s
Module 7/63 org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car started in .188s
Module 8/63 org.apache.geronimo.configs/j2ee-server/3.0-SNAPSHOT/car started in .031s
Module 9/63 org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car started in .078s
Module 10/63 org.apache.geronimo.configs/bval-deployer/3.0-SNAPSHOT/car started in .141s
Module 11/63 org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car started in .125s
Module 12/63 org.apache.geronimo.configs/system-database/3.0-SNAPSHOT/car started in .781s
Module 13/63 org.apache.geronimo.configs/openjpa2/3.0-SNAPSHOT/car 2011-08-22 14:54:47
no longer available for use with the Aries Blueprint container
started in .000s
Module 14/63 org.apache.geronimo.configs/openejb/3.0-SNAPSHOT/car started in .578s
Module 15/63 org.apache.geronimo.configs/jasper/3.0-SNAPSHOT/car started in .016s
Module 16/63 org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car started in .718s
Module 17/63 org.apache.geronimo.configs/connector-deployer-1_6/3.0-SNAPSHOT/car started in .047s
Module 18/63 org.apache.geronimo.configs/tomcat7-deployer/3.0-SNAPSHOT/car started in .016s
Module 19/63 org.apache.geronimo.configs/web-extender/3.0-SNAPSHOT/car started in .016s
Module 20/63 org.apache.geronimo.configs/hot-deployer/3.0-SNAPSHOT/car
______ _
/ ____/___ _________ ____ (_)____ ___ ____
/ / __ / _ \/ ___/ __ \/ __ \/ // __ `__ \/ __ \
/ /_/ // __/ / / /_/ / / / / // / / / / / /_/ /
\____/ \___/_/ \____/_/ /_/_//_/ /_/ /_/\____/
Apache Geronimo (3.0-SNAPSHOT)
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Geronimo.
geronimo> started in .031s
Module 21/63 org.apache.geronimo.configs/remote-deploy-tomcat/3.0-SNAPSHOT/car started in .547s
Module 22/63 org.apache.geronimo.configs/jasper-deployer/3.0-SNAPSHOT/car started in .000s
Module 23/63 org.apache.geronimo.configs/myfaces/3.0-SNAPSHOT/car started in .000s
Module 24/63 org.apache.geronimo.configs/myfaces-deployer/3.0-SNAPSHOT/car started in .312s
Module 25/63 org.apache.geronimo.configs/aries/3.0-SNAPSHOT/car started in .000s
Module 26/63 org.apache.geronimo.configs/aries-deployer/3.0-SNAPSHOT/car started in .000s
Module 27/63 org.apache.geronimo.configs/persistence-jpa20-deployer/3.0-SNAPSHOT/car started in .000s
Module 28/63 org.apache.geronimo.plugins/pluto-support/3.0-SNAPSHOT/car started in .000s
Module 29/63 org.apache.geronimo.plugins/console-tomcat/3.0-SNAPSHOT/car started in 1.297s
Module 30/63 org.apache.geronimo.plugins/plugin-console-tomcat/3.0-SNAPSHOT/car started in .375s
Module 31/63 org.apache.geronimo.plugins.monitoring/mconsole-ds/3.0-SNAPSHOT/car started in .047s
Module 32/63 org.apache.geronimo.plugins.monitoring/mconsole-tomcat/3.0-SNAPSHOT/car started in 1.047s
Module 33/63 org.apache.geronimo.configs/activemq-broker-blueprint/3.0-SNAPSHOT/car started in 1.110s
Module 34/63 org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car started in .187s
Module 35/63 org.apache.geronimo.plugins/activemq-console-tomcat/3.0-SNAPSHOT/car started in .406s
Module 36/63 org.apache.geronimo.plugins/debugviews-console-tomcat/3.0-SNAPSHOT/car started in .344s
Module 37/63 org.apache.geronimo.plugins/sysdb-console-tomcat/3.0-SNAPSHOT/car started in .484s
Module 38/63 org.apache.geronimo.plugins/openejb-console-tomcat/3.0-SNAPSHOT/car started in .516s
Module 39/63 org.apache.geronimo.configs/openejb-deployer/3.0-SNAPSHOT/car started in .031s
Module 40/63 org.apache.geronimo.configs/openejb-corba-deployer/3.0-SNAPSHOT/car started in .031s
Module 41/63 org.apache.geronimo.configs/j2ee-corba-yoko/3.0-SNAPSHOT/car started in .313s
Module 42/63 org.apache.geronimo.configs/openwebbeans-deployer/3.0-SNAPSHOT/car started in .016s
Module 43/63 org.apache.geronimo.plugins.monitoring/agent-ds/3.0-SNAPSHOT/car started in .235s
Module 44/63 org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car started in .516s
Module 45/63 org.apache.geronimo.plugins.monitoring/agent-car-jmx/3.0-SNAPSHOT/car started in .031s
Module 46/63 org.apache.geronimo.configs/welcome-tomcat/3.0-SNAPSHOT/car started in .391s
Module 47/63 org.apache.geronimo.configs/javamail/3.0-SNAPSHOT/car started in .016s
Module 48/63 org.apache.geronimo.plugins/plancreator-console-tomcat/3.0-SNAPSHOT/car started in .390s
Module 49/63 org.apache.geronimo.configs/client-deployer/3.0-SNAPSHOT/car started in .047s
Module 50/63 org.apache.geronimo.configs/webservices-common/3.0-SNAPSHOT/car started in .000s
Module 51/63 org.apache.geronimo.configs/axis/3.0-SNAPSHOT/car started in .047s
Module 52/63 org.apache.geronimo.configs/axis-deployer/3.0-SNAPSHOT/car started in .031s
Module 53/63 org.apache.geronimo.configs/jaxws-deployer/3.0-SNAPSHOT/car started in .000s
Module 54/63 org.apache.geronimo.configs/axis2/3.0-SNAPSHOT/car started in .218s
Module 55/63 org.apache.geronimo.configs/axis2-deployer/3.0-SNAPSHOT/car started in .016s
Module 56/63 org.apache.geronimo.configs/jaxws-ejb-deployer/3.0-SNAPSHOT/car started in .000s
Module 57/63 org.apache.geronimo.configs/axis2-ejb-deployer/3.0-SNAPSHOT/car started in .016s
Module 58/63 org.apache.geronimo.configs/jaxws-sun-tools/3.0-SNAPSHOT/car started in .000s
Module 59/63 org.apache.geronimo.configs/jaxws-tools/3.0-SNAPSHOT/car started in .000s
Module 60/63 org.apache.geronimo.plugins/uddi-db/3.0-SNAPSHOT/car started in .031s
Module 61/63 org.apache.geronimo.configs/uddi-tomcat/3.0-SNAPSHOT/car started in 2.922s
Module 62/63 org.apache.geronimo.configs/wink/3.0-SNAPSHOT/car started in .000s
Module 63/63 org.apache.geronimo.configs/wink-deployer/3.0-SNAPSHOT/car started in .016s
Startup completed in 40.688s seconds
-----------------------------------------------------------------------------------
-Rex
> Display usage information after server startup?
> -----------------------------------------------
>
> Key: GERONIMO-6077
> URL: https://issues.apache.org/jira/browse/GERONIMO-6077
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Reporter: Kevan Miller
>
> The usage information:
> {code}
> Hit '<tab>' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Geronimo.
> {code}
> Would be better displayed after a server startup is complete. Also, the command prompt (i.e. 'geronimo>') is not visible after the server has been started. So, it's not apparent to new users that they can enter a command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6077) Display usage information after
server startup?
Posted by "Yi Xiao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065653#comment-13065653 ]
Yi Xiao commented on GERONIMO-6077:
-----------------------------------
Hi, Kevan, the command prompt 'geronimo>' is visible, but after show it, the geronimo modules' start infos are outputted, so it seems like no 'geronimo>' is visible~
> Display usage information after server startup?
> -----------------------------------------------
>
> Key: GERONIMO-6077
> URL: https://issues.apache.org/jira/browse/GERONIMO-6077
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Reporter: Kevan Miller
>
> The usage information:
> {code}
> Hit '<tab>' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Geronimo.
> {code}
> Would be better displayed after a server startup is complete. Also, the command prompt (i.e. 'geronimo>') is not visible after the server has been started. So, it's not apparent to new users that they can enter a command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6077) Display usage information after
server startup?
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065683#comment-13065683 ]
Kevan Miller commented on GERONIMO-6077:
----------------------------------------
Right. Which is really what I meant. The 'geronimo>' prompt (and the usage information) has typically scrolled off the screen and is probably 'no longer visible' to the user.
> Display usage information after server startup?
> -----------------------------------------------
>
> Key: GERONIMO-6077
> URL: https://issues.apache.org/jira/browse/GERONIMO-6077
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Reporter: Kevan Miller
>
> The usage information:
> {code}
> Hit '<tab>' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Geronimo.
> {code}
> Would be better displayed after a server startup is complete. Also, the command prompt (i.e. 'geronimo>') is not visible after the server has been started. So, it's not apparent to new users that they can enter a command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira