- How do I avoid cluster cross talk when using TCP-based clusters?
- How to avoid overlapping clusters when using TCP-based clusters?
- In a clustered (TCP) setup of JBoss, we often find the following messages.
[org.jgroups.protocols.TCP] discarded message from different group "OtherPartition" (our group is "MyPartition"). Sender was 192.168.0.1:1234</code>
In later JBoss EAP versions, messages may appear like such:
WARN [org.jgroups.protocols.TCP] (thread-3) JGRP000012: discarded message from different cluster ee (our cluster is ejb). Sender was 1f277e10-4ef6-6904-4c26-294dbc1f0bdd (received 3 identical messages from 1f277e10-4ef6-6904-4c26-294dbc1f0bdd in the last 115982 ms)
- Red Hat JBoss Enterprise Application Platform (EAP)
- All Versions
- TCP Clustering
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.