[jboss-user] [Clustering/JBoss] - Re: discarded message from non-member

bstansberry@jboss.com do-not-reply at jboss.com
Mon Jan 19 12:38:21 EST 2009

First, if you are a support customer (you're using EAP), please open a case via the Customer Support Portal. There's no SLA via the forums.


1) Are you actually using UDP multicast?  The ports shown in your logs seem more like what would be used by a TCP-based JGroups config. (Could be multicast though; depends on your config).

2) I need to understand what channels are using and  Please find the logging that looks like this on the two nodes and post the area around it:

GMS: address is


GMS: address is

3) The following will likely cause problems, although AFAIR not the NAKACK issue you are reporting:

15:50:45,995 INFO [DefaultPartition] All Members : 2 ([,]) 

That tells me you have JBoss bound to on both nodes. That would occur either by starting JBoss with -b on both nodes, or by not setting -b and leaving the default. The AS clustering code uses the bind address and JNDI port to form a unique cluster-wide id for each node. Works fine, except when you bind JBoss to or on more than one machine. If you *want* to use or as the -b value on more than one node, you should edit the server/all/deploy/cluster-service.xml's ClusterPartition mbean and either change


to something unique per server, like

or, explicitly configure a String "NodeName" attribute with a unique value per node:


Bottom line, you don't want duplicates in the "[DefaultPartition] All Members" logging.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202979#4202979

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202979

More information about the jboss-user mailing list