permaculture playing cards*
The moose likes JBoss/WildFly and the fly likes Port Numbers to be used in a JBOSS Cluster over TCP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Port Numbers to be used in a JBOSS Cluster over TCP" Watch "Port Numbers to be used in a JBOSS Cluster over TCP" New topic

Port Numbers to be used in a JBOSS Cluster over TCP

Antonio Xavier Annasamy

Joined: May 11, 2009
Posts: 3
Hi All

I have managed to create a horizontal JBOSS cluster over TCP in our environment. The files which needed the cluster config changes are:

1. $JBOSS_HOME/server/<instance name>/deploy/cluster-service.xml
2. $JBOSS_HOME/server/<instance name>/deploy/ejb3-clustered-sfsbcache-service.xml
3. $JBOSS_HOME/server/<instance name>/deploy/ejb3-entity-cache-service.xml
4. $JBOSS_HOME/server/<instance name>/deploy/jboss-web-cluster.sar/META-INF/jboss-service.xml

(Please let me know, if I have missed out any other files.)

Now in all the above files when I used port number 7800. The cluster is formed, but there are messages which get generated about packets being dropped.
For example
cluster-service.xml from one node tries to connect to ejb3-clustered-sfsbcache-service.xml or ejb3-entity-cache-service.xml or META-INF/jboss-service.xml of the second node.
But the second node denies this request due to a different name and drops the request. (The cluster is still intact. Same files across different nodes are in communication, but cross file communication is dropped)
Is this normal? Is this how it should be?

To avoid these messages I have configured different ports for the above files across the cluster.
For example:
Port number in cluster-service.xml across all nodes is 7800
Port number in ejb3-clustered-sfsbcache-service.xml across all nodes is 7900
Port number in ejb3-entity-cache-service.xml across all nodes is 7950
Port number in META-INF/jboss-service.xml across all nodes is 8000

Is this approach correct? I haven't tested this setup with any application yet, but will be doing it later.

Please let me know if I am doing this wrong



I agree. Here's the link:
subject: Port Numbers to be used in a JBOSS Cluster over TCP
Similar Threads
JBOSS 4.3.0 EAP Clustering with Apache HTTP Server 2.2.11
Apache/Jboss via mod_jk loadbalancing/failover not seeing other node in cluster and mcast_addr wrong
Possible to clear or disable JBoss3/EJB2 cache?
Unique node during installation.
How To use the Scheduler Service on JBoss