Multiple Instances of WildFly on Different Ports on Same Machine (Tech Tip #8)

January 12, 2014 by arungupta in techtip, wildfly

WildFly can be started on the default port 8080 using:

./bin/standalone.sh

The default landing page is then accessible at localhost:8080 and looks like:

The default admin console is accessible at localhost:9990/console and looks like:

Do you want to start another WildFly standalone instance on the same machine on a different port ?

./bin/standalone.sh -Djboss.socket.binding.port-offset=1000

will start another standalone server on port 8080 + 1000. And so the landing page is now accessible at localhost:9080. Similarly, admin console is now accessible at localhost:10990/console.

Similarly, you can start multiple instances by specifying port offset.

Be Sociable, Share!

• 
• 

• Tweet
• 

Related posts:

1. Deploy to WildFly using curl (Tech Tip #10)
2. Deploy to WildFly using jboss-cli (Tech Tip #11)
3. WildFly 8 CR1 on OpenShift (Tech Tip #7)
4. Getting Started with WildFly (TechTip #1)
5. WildFly Maven Plugin to Deploy Applications and Artifacts (Tech Tip #9)

Tags: wildfly

• ← DevNation: Announcing New Conference for Open Source and Polyglot Developers
• WildFly Maven Plugin to Deploy Applications and Artifacts (Tech Tip #9) →

5 Responses to “Multiple Instances of WildFly on Different Ports on Same Machine (Tech Tip #8)”

1. muppet tizer says:

   January 12, 2014 at 12:19 pm

   Hi Arun,

   Any tutorial on how to setup WilFly JEE clustering, with details like:
   – load balancer
   – how http session and stateful ejbs data is replicated to a backup cluster instance
   – failover
   – scaling
   – integration with in-memory data grids
2. arungupta says:

   January 12, 2014 at 12:25 pm

   WildFly 8 docs are available at:

   https://docs.jboss.org/author/display/WFLY8/Documentation

   High Availability Guide (work in progress) is available at:

   https://docs.jboss.org/author/display/WFLY8/High+Availability+Guide

   I’ll blog about it in the next few weeks with detailed steps.
3. Igor says:

   March 27, 2014 at 12:39 pm

   Hi Arun,

   Nice article. I am working on one test app in cluster environment. I have deployed remote stateless ejb on cluster (node A and node B in domain mode). I start one more standalone instance on node A and try to deploy a client app. Issue is that client cannot connect to ejb on node A while it connects to node B without any problems. If I put client on node B also on standalone instance it cannot connect to ejb on node B but can connect to node A.
   Is this expected behavior or I’m missing something? Any link or tutorial will be mostly appreciated. My goal is to have one cluster where I will deploy remote stateless ejb in one server group and client on the same cluster under other server group which will communicate with both nodes. Is this possible? Thanks.
4. arungupta says:

   March 27, 2014 at 3:35 pm

   Can you post your question to WildFly forum at https://community.jboss.org/en/wildfly ?
5. Jdeveloper says:

   July 4, 2014 at 5:59 am

   We created an app that runs on wildfly.8.1.0.Final, but I must use two diffrent machines running wildfly for load balancing and fail over, can you help with this? Or do you know where I can look for some info on this?