WildFly Cookbook

Binding WildFly onto a custom port

Why would you bind WildFly onto a custom port? This is because you might have a different service running on the same IP:PORT (that is, another WildFly or JBoss instance, Tomcat, or GlassFish).

How to do it...

Just open your command line and launch your WildFly standalone instance as follows:

$ cd $WILDFLY_HOME
$ ./bin/standalone.sh

Now you can change the port using either the Web Console or the CLI:

Using the Web Console

1. Point your browser to the following address: http://127.0.0.1:8080/console.
2. Log in by entering the credentials specified in Chapter 1, Welcome to WildFly! while adding the management user; we entered wildfly as the username and cookbook.2015 as the password.
3. Select the Configuration tab and select from ...