Configure JBoss network ports

This form is only shown when Application Server Type is JBoss and Extended Server or Web Client is deployed.
JBoss uses a number of network ports for communication with both external clients and internally within the server instance. This form lets you change those port numbers. You need to change port numbers if they are already in use on the computer. If you are creating additional instances, you will need to use a unique port set for each instance to avoid port conflicts when to running them in parallel. The installation tool does not validate if the ports are available for use on the computer.

Note: For most ports, it is not important to know their configuration. They are used internally by JBoss and the only requirement is that there is no other application on the computer using them. Exceptions to this rule: AJP13 port may have to be known to administrators doing manual web server configuration. HTTP port must be known, when enabled and in use, to all clients. Java Remote Debugging port must be known to developers wanting to do remote debugging of applications.

JBoss network port configuration

Actions

1. If you want to change all port numbers in one go, you can do it by changing the Port Prefix. When the port prefix is changed, all port numbers starting with that prefix are also changed accordingly. You can use any port prefix between 41 and 65.
2. You can prepare your own binding file where you can define ports according to your needs. If you have such file, tick in checkbox Custom bindings and use the Browse button to point out the file. The file will replace standard JBoss binding file. Read more about JBoss binding concept at http://community.jboss.org/wiki/AS5ServiceBindingManager.
3. If you choose to use your own binding file, you have to enter name for a valid Binding set to use. A binding set is a logical group of port definitions you specify in your binding file. You can have several sets defined in the binding file, but only one will be used for this JBoss instance. Enter the name of the Binding set here:
   
   
   On Unix/Linux there's an additional Naming port parameter which you need to specify as well. Among other ports your binding set specifies a port for JNDI naming service, which is used by the start script for JBoss running status control and shutdown. Enter the port number here:
   
4. Press Next

Verify

	NA
	If you get an error saying java.net.BindException: Address already in use: JVM_Bind when you start the JBoss server instance (after installation), then you have a port conflict and need to reconfigure the instance with a different port set. The error message also prints the port number for which there is a conflict.