JBoss start up configuration
| Article Index |
|---|
| JBoss start up configuration |
| Setting Server properties using the Properties Service |
| Logging the startup process |
| All Pages |
This short tutorial explains all the things you need to know about the startup process of JBoss AS, how to inject system properties in the application server and how to trace the logs of the start up activities.
How to start the JBoss AS
Starting the application server is just a matter of launching the start.cmd (Windows) or start.sh (Unix) script.
You can however customize the server startup using several parameters:
The option -b can be used to bind all server services to an IP Address.
For example:
run.sh -b 192.168.10.1 # Bind the server on the IP Address 192.168.10.1
run.sh -b 0.0.0.0 # Bind the server on all network interfaces
The option -c can be used to choose which server configuration will be started. If not used the "default" will be chosen.
For example:
run.sh -c all # Starts the "all" server configuration
The options -B can be used to add an extra library to the front bootclasspath
This is equivalento to dropping a jar library into $JBOSS_HOME/lib.
The options -L can be used to add an extra library to the loaders classpath
This is equivalento to dropping a jar library into $JBOSS_HOME/common/lib.
You can set a system property through the
-D<name>=<value> option. You can also use the -P option to load the properties from a file.
Example:
Create a file named test.properties
jboss.bind.address=0.0.0.0
jboss.service.binding.set=ports-default
launch JBoss AS with:
run.cmd -P test.properties
Applications using JGroups library might benefit from the -m and -u option.
-m sets the UDP multicast port; only used by JGroups. -u sets the UDP multicast address

