JBoss.org Community Documentation
After you have installed the JBoss Application Server, 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, open the JBOSS_DIST/jboss-<release>/bin
directory and execute the run.bat
(for Windows) or run.sh
(for Linux) script, as appropriate for your operating system.
Your output should look similar to the following (accounting for installation directory differences) and contain no error or exception messages:
[samson@dhcp-1-150 bin]$ sh run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /downloads/jboss-5.0.0.CR2 JAVA: /usr/local/jdk1.6.0_07//bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true CLASSPATH: /downloads/jboss-5.0.0.CR2/bin/run.jar:/usr/local/jdk1.6.0_07//lib/tools.jar ========================================================================= 15:23:05,038 INFO [ServerImpl] Starting JBoss (Microcontainer)... 15:23:05,042 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139) . . ...output truncated . . 15:25:18,401 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 15:25:18,556 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 15:25:18,620 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)] Started in 2m:13s:511ms
Now open http://localhost:8080
in your web browser. (Make sure you dont have anything else already on your machine using that port).[2] The contents of your page should look similar to the following: Figure 7.1, “Test your Installation”.
You are now ready to use the JBoss Application Server.
[2] Note that on some machines, the name localhost may not resolve properly and you may need to use the local loopback address 127.0.0.1 instead.