Managing Ports with Multiple Instances of JBoss EAP on one Server
2.4 Managing Ports with Multiple Instances of JBoss EAP on one Server JBoss EAP is a lighter application server (and can be made even lighter based on your needs). Because of this along with the immense gains in hardware performance and low cost of hardware, most JBoss customer deploy multiple instances of JBoss EAP in a single server (virtual and physical). When deploying multiple instances of JBoss EAP on one server, it is best to use the same recommendation from above – leveraging the startup flag to your run script to create port offsets. The two largest concerns with multiple instances is resource availability (outside the scope of this document) and port contention. Starting up your instances using the same configuration template (all, production, default, your custom, etc) and just leveraging the startup flag to guarantee ports won’t conflict is your best and safest bet. We looked at that in detail in the previous section. As a refresher, you will want to use the -Djboss.service.binding.set flag during startup, passing it ports-01, ports-02, or ports-03. ie: ./run.sh -c node2 -g ClusterGroup -u 239.255.100.100 -b 127.0.0.1 -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01