[
https://issues.jboss.org/browse/WFLY-4971?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-4971:
------------------------------------
[~witoldbolt] For WF9, you have 2 options:
# Use a designated protocol stack for messaging-activemq. This entails using a unique
transport socket-binding to isolate the 2 clusters.
# Just configure jgroups to stop logging those warnings (they are harmless anyway). To do
that, add this to your jgroups subsystem configuration:
{code:xml}
<stack name="udp">
<transport type="UDP">
<property name="log_discard_msgs property">false</property>
</transport>
</transport>
{code}
#2 is by far the simplest solution.
lots of warnings discarded message from different cluster
---------------------------------------------------------
Key: WFLY-4971
URL:
https://issues.jboss.org/browse/WFLY-4971
Project: WildFly
Issue Type: Bug
Affects Versions: 9.0.0.Final
Reporter: Daniele Pirola
Assignee: Paul Ferraro
I run the latest wildfly-9.0.0.Final. I have an environment with 2 host and 3 server per
host. I noticed that there are a lot of warning like this
JGRP000012: discarded message from different cluster hq-cluster (our cluster is ee)
or this
JGRP000012: discarded message from different cluster ee (our cluster is hq-cluster)
With the same configuration in wildfly-8.2.0.Final I didn't noticed anything.
The strange thing is that warnings still appear even if I run only the domain controller
with 1 server active. I think that the domain configuration (I used the default with
full-ha profile) is missing something that can diffentiate jgroup channel but I don't
know how
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)