Move to JBOSS_DIST/jboss-as/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 like the following (accounting for installation directory differences) and contain no error or exception messages:
[jwulf@thinkpad bin]$ ./run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jwulf/jboss-eap-4.2/jboss-as JAVA: java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.client. gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jwulf/jboss-eap-4.2/jboss-as/bin/run.jar ========================================================================= 13:11:46,215 INFO [Server] Starting JBoss (MX MicroKernel)... . . . . 13:11:47,071 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc. 13:11:47,071 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc. 13:11:47,072 INFO [ServerInfo] OS-System: Linux 2.6.21-1.3228.rhel5,i386 13:11:48,558 INFO [Server] Core system initialized 13:11:56,934 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/ 13:11:56,940 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
Note that there is no "Server Started" message shown at the console when the server is started using the production profile, which is the default profile used when no other is specified. This message may be observed in the server.log file located in the server/production/log subdirectory.