It has been observed that in wildfly deployments, when we are running the application on wildfly offset 200 means port 8280 and the root cause of this issue is wildfly internally launch its Jgroup at default port 7600 which gets modified based on offset values (so for offset 200, wildfly’s jgroup port = 7600 + 200 = 7800). So for example if the Insight is already running on port 7800 (CLUSTER_TCP_START_PORT=7800 setting set by default in appserver.advanced.properties), other application for example, IV does not get that port and throws the below error:
java.net.BindException: no port available in range [7800 .. 7800]
Follow the below steps: In our example, we will assume, Perceive is having the port conflict issue when Insight is up and running.
- Modify the below property to 7850 as shown for Insight:
- Modify the below property to 7950 as shown for Perceive:
- Run clean and deploy