2.3. Starting and Stopping the Server
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:
[vrenish@vinux bin]$ ./run.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/vrenish/EnterprisePlatform-4.3.0/jboss-as
JAVA: /usr/java/jdk1.5.0_11/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djava.net.prefer IPv4Stack=true
CLASSPATH: /home/vrenish/EnterprisePlatform-4.3.0/jboss-as/bin/run.jar:/u sr/java/jdk1.5.0_11/lib/tools.jar
=========================================================================
14:52:06,251 INFO [Server] Starting JBoss (MX MicroKernel)...
.
.
.
14:52:07,630 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
14:52:07,631 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03 ,Sun Microsystems Inc.
14:52:07,631 INFO [ServerInfo] OS-System: Linux 2.6.9-42.0.3.EL,i386
14:52:11,251 INFO [Server] Core system initialized
14:52:18,230 INFO [WebService] Using RMI server codebase: https://127.0.0.1:8083/
14:52:18,233 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
Note
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.