Child pages
  • startup
Skip to end of metadata
Go to start of metadata

This command is certainly used to start the Apache Geronimo server. You can start the Apache Geronimo server in two different ways by running the following commands:

<geronimo_home>/bin/java -jar server.jar

or simply


The startup command invokes the server.jar.

In both cases this command accepts the same parameters. The available parameters are:

Suppress the normal startup progress bar. This is typically used when redirecting console output to a file, or starting the server from an IDE or other tool.

Write startup progress to the console in a format that is suitable for redirecting console output to a file, or starting the server from an IDE or other tool (does not use linefeeds to update the progress information that is used by default if you do not specify --quiet or --long).

-v --verbose
Sets the console log level to INFO, resulting in more console output than is normally present.

-vv --veryverbose
Sets the console log level to DEBUG, resulting in even more console output.

-override [configId]
Overrides the configurations in <geronimo_home>/var/config.list such that only the configurations listed on the command line will be started. Note that many J2EE
features depend on certain configs being started, so you should be very careful what you omit. Any arguments after -override are assumed to be configuration names.

When you run this command from a Microsoft Windows command line that window will get locked with the startup results screen. On a Linux based operating system you can run this command in background getting back the control for this window terminal.

If you run the startup command without any parameters you will see a screen similar to this one.

Booting Geronimo Kernel (in Java 1.4.2_09)...
Configuration geronimo/rmi-naming/1.1/car started in  1/20   1s
Configuration geronimo/j2ee-server/1.1/car started in  2/20   1s
Configuration geronimo/j2ee-security/1.1/car started in  3/20   2s
Configuration geronimo/axis/1.1/car started in  4/20   0s
Configuration geronimo/openejb/1.1/car started in  5/20   0s
Configuration geronimo/system-database/1.1/car started in  6/20  14s
Configuration geronimo/activemq-broker/1.1/car started in  7/20   5s
Configuration geronimo/activemq/1.1/car started in  8/20   1s
Configuration geronimo/tomcat/1.1/car started in  9/20   4s
Configuration geronimo/geronimo-gbean-deployer/1.1/car started in 10/20   1s
Configuration geronimo/j2ee-deployer/1.1/car started in 11/20   0s
Configuration geronimo/openejb-deployer/1.1/car started in 12/20   0s
Configuration geronimo/client-deployer/1.1/car started in 13/20   0s
Configuration geronimo/axis-deployer/1.1/car started in 14/20   0s
Configuration geronimo/sharedlib/1.1/car started in 15/20   0s
Configuration geronimo/tomcat-deployer/1.1/car started in 16/20   0s
Configuration geronimo/welcome-tomcat/1.1/car started in 17/20   0s
Configuration geronimo/webconsole-tomcat/1.1/car started in 18/20   4s

Configuration geronimo/remote-deploy-tomcat/1.1/car started in 19/20   0s
Configuration geronimo/hot-deployer/1.1/car started in 20/20   0s
Startup completed in 39 seconds
  Listening on Ports:
    1099   RMI Naming
    1527   Derby Connector
    4201   ActiveIO Connector EJB
    4242 Remote Login Listener
    8009   Tomcat Connector AJP
    8080   Tomcat Connector HTTP
    8443   Tomcat Connector HTTPS
    9999   JMX Remoting Connector
   61616   ActiveMQ Message Broker Connector

  Started Application Modules:
    EAR: geronimo/webconsole-tomcat/1.1/car
    RAR: geronimo/activemq/1.1/car
    RAR: geronimo/system-database/1.1/car
    WAR: geronimo/remote-deploy-tomcat/1.1/car
    WAR: geronimo/welcome-tomcat/1.1/car

  Web Applications:

Geronimo Application Server started

  • No labels