FD_SOCK SUSPECT messages in JBoss log when clustering across subnets

Solution Verified - Updated -

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5

Issue

JBoss has been working in a cluster on the same subnet, but when testing a cluster split across subnets.

INFO  [org.jboss.cache.RPCManagerImpl] (Incoming-9,10.1.2.2:7600) Received new cluster view: [10.1.2.2:7600|6] [10.1.2.2:7600, 10.1.2.3:7600, 10.1.1.3:7600]
WARN  [org.jgroups.protocols.FD_SOCK] (OOB-17,10.1.2.2:7600) I was suspected by 10.1.1.3:7600; ignoring the SUSPECT message
WARN  [org.jgroups.protocols.FD_SOCK] (OOB-17,10.1.2.2:7600) I was suspected by 10.1.1.3:7600; ignoring the SUSPECT message

Resolution

Change the firewall to allow FD_SOCK traffic to pass.

https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Security_Guide/chap-Firewalls.html

Root Cause

A firewall between the two halves of the cluster was dropping FD_SOCK traffic. This causes a node to immediately SUSPECT a node on the other side when it is setting up the FD_SOCK sockets after the cluster initially forms.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments