Move to
$JBOSS_HOME/jboss-as-web/bin directory and execute the run.bat (for Windows) or run.sh (for Linux) script, as appropriate for your operating system.
There is no
Server Started message shown at the console when the server is started using the production profile. This message can be found in the server.log file located in the $JBOSS_HOME/jboss-as-web/server/$PROFILE/log subdirectory.
Remote connection to the JBoss Enterprise Web Platform server
The JBoss Enterprise Web Platform now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run JBoss with the
-b option. To bind to all available interfaces and re-enable the legacy behaviour use ./run.sh -b 0.0.0.0 on Linux or run.bat -b 0.0.0.0 on Windows. In any case, be aware you still need to secure your server properly.
Using
-b as part of the JBoss web server's command line is equivalent to setting these individual properties: -Djboss.bind.address, -Djava.rmi.server.hostname, -Djgroups.bind_addr and -Dbind.address. Passing -Djboss.bind.address to the Java process as part of the JAVA_OPTS variable in the run scripts will not work as it is a JBoss property not a JVM property.
For more information including setting up multiple JBoss web server instances on one machine and hosting multiple domains with JBoss, please refer to the Administration and Configuration Guide for this distribution of JBoss Enterprise Web Platform.
On starting your server, your screen output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
[user@mypc bin]$ ./run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME:unzip_location/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:unzip_location/jboss-as =========================================================================
More options for the JBoss Enterprise Web Platform
run script are discussed in Section 1.2.2, “Start the Server With Alternate Configuration”.
Note
There is no Server Started message shown at the console when the server is started using the
production profile. This message may be observed in the server.log file located in the server/$PROFILE/log subdirectory.