Basic Installation Testing

After you have installed the JBoss distribution, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. To test your installation, move to the JBOSS_DIST/bin directory and execute the run.bat or run.sh script, as appropriate for your operating system. Your output should be similar to the following, and it should contain no error or exception messages:

[View full width]
 [bin]$ sh run.sh =========================================================================   JBoss Bootstrap Environment   JBOSS_HOME: /tmp/jboss-4.0.1      JAVA: /System/Library/Frameworks/JavaVM.framework/Home//bin/java   JAVA_OPTS: -server -Xms128m -Xmx128m -Dprogram.name=run.sh   CLASSPATH: /tmp/jboss-4.0.1/bin/run.jar:/System/Library/Frameworks/JavaVM.framework/Home //lib/tools.jar ========================================================================= 17:29:04,702 INFO  [Server] Starting JBoss (MX MicroKernel)... 17:29:04,715 INFO  [Server] Release ID: JBoss [Zion] 4.0.1RC2 (build:  CVSTag=JBoss_4_0_1_RC2 date=200411302349) 17:29:04,746 INFO  [Server] Home Dir: /private/tmp/jboss-4.0.1 17:29:04,748 INFO  [Server] Home URL: file:/private/tmp/jboss-4.0.1/ 17:29:04,751 INFO  [Server] Library URL: file:/private/tmp/jboss-4.0.1/lib/ 17:29:04,756 INFO  [Server] Patch URL: null 17:29:04,759 INFO  [Server] Server Name: default 17:29:04,776 INFO  [Server] Server Home Dir: /private/tmp/jboss-4.0.1/server/default 17:29:04,778 INFO  [Server] Server Home URL: file:/private/tmp/jboss-4.0.1/server/default/ 17:29:04,781 INFO  [Server] Server Data Dir: /private/tmp/jboss-4.0.1/server/ default/data 17:29:04,784 INFO  [Server] Server Temp Dir: /private/tmp/jboss-4.0.1/server/ default/tmp 17:29:04,787 INFO  [Server] Server Config URL: file:/private/tmp/jboss-4.0.1/server /default/conf/ 17:29:04,789 INFO  [Server] Server Library URL: file:/private/tmp/jboss-4.0.1/server /default/lib/ 17:29:04,791 INFO  [Server] Root Deployment Filename: jboss-service.xml 17:29:04,833 INFO  [Server] Starting General Purpose Architecture (GPA)... 17:29:06,121 INFO  [ServerInfo] Java version: 1.4.2_05,Apple Computer, Inc. 17:29:06,124 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2-38, "Apple Computer, Inc." 17:29:06,127 INFO  [ServerInfo] OS-System: Mac OS X 10.3.6,ppc 17:29:07,236 INFO  [Server] Core system initialized ... 17:29:49,550 INFO  [Server] JBoss (MX MicroKernel) [4.0.1RC2 (build: CVSTag= JBoss_4_0_1_RC2 date=200411302349)] Started in 44s:3ms 

If your output is similar to this (accounting for installation directory differences), you should now be ready to use JBoss. To shut down the server, you simply issue a Ctrl+C sequence in the console in which JBoss was started. Alternatively, you can use the shutdown.sh command:

 [bin]$ ./shutdown.sh A JMX client to shutdown (exit or halt) a remote JBoss server. usage: shutdown [options] <operation> options:     -h, --help                Show this help message     -D<name>[=<value>]        Set a system property     --                        Stop processing options     -s, --server=<url>        Specify the JNDI URL of the remote server     -n, --serverName=<url>    Specify the JMX name of the ServerImpl     -a, --adapter=<name>      Specify JNDI name of the RMI adapter to use     -u, --user=<name>         Specify the username for authentication[not implemented yet]     -p, --password=<name>     Specify the password for authentication[not implemented yet] operations:      -S, --shutdown            Shutdown the server (default)     -e, --exit=<code>         Force the VM to exit with a status code     -H, --halt=<code>         Force the VM to halt with a status code 

Using run.sh without any arguments starts the server, using the default server configuration file set. To start with an alternate configuration file set, you pass in the name of the directory under JBOSS_DIST/server that you wish to use as the value to the -c command-line option. For example, to start with the minimal configuration file set, you would specify this:

 [bin]$ ./run.sh -c minimal ... 17:40:41,092 INFO  [Server] JBoss (MX MicroKernel) [4.0.1RC2 (build: CVSTag= JBoss_4_0_1_RC2 date=200411302349)] Started in 4s:920ms 

To view all the supported command-line options for the JBoss server bootstrap class, you issue the run-h command, and the output looks like this:

 usage: run.sh [options] options:     -h, --help                    Show this help message     -V, --version                 Show version information     --                            Stop processing options     -D<name>[=<value>]            Set a system property     -p, --patchdir=<dir>          Set the patch directory; Must be absolute     -n, --netboot=<url>           Boot from net with the given url as base     -c, --configuration=<name>    Set the server configuration name     -j, --jaxp=<type>             Set the JAXP impl type (ie. crimson)     -B, --bootlib=<filename>      Add an extra library to the front bootclasspth     -L, --library=<filename>      Add an extra library to the loaders classpath     -C, --classpath=<url>         Add an extra url to the loaders classpath     -P, --properties=<url>        Load system properties from the given url     -b, --host=<host or ip>       Bind address for all JBoss services