[
https://issues.jboss.org/browse/WFLY-9371?page=com.atlassian.jira.plugin....
]
Radoslav Husar edited comment on WFLY-9371 at 9/26/17 10:41 AM:
----------------------------------------------------------------
The problem according to logs is clear
{noformat}
2017-09-26 15:58:11,689 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport]
(MSC service thread 1-5)
ISPN000094: Received new cluster view for channel web: [clusterA-node0|2] (3)
[clusterA-node0, clusterA-node1, clusterB-node0]
{noformat}
because {{jboss.default.multicast.address}} is provided with the same value on the system
boot.
was (Author: rhusar):
The problem according to logs is clear
{noformat}
2017-09-26 15:58:11,689 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport]
(MSC service thread 1-5) ISPN000094: Received new cluster view for channel web:
[clusterA-node0|2] (3) [clusterA-node0, clusterA-node1, clusterB-node0]
{noformat}
because {{jboss.default.multicast.address}} is provided with the same value on the system
boot.
Fix failing RemoteEJBTwoClusterTestCase
---------------------------------------
Key: WFLY-9371
URL:
https://issues.jboss.org/browse/WFLY-9371
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.1.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
The problem is that this test is not run as part of regular CI execution thus is destined
to be broken. The test should be run as part of regular CI set of tests; if intermittently
failing then it should be @Ignore-d in the way intermittently failing tests are.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)