[
https://jira.jboss.org/jira/browse/JGRP-830?page=com.atlassian.jira.plugi...
]
Bela Ban commented on JGRP-830:
-------------------------------
I tested this, but I'm not sure what to do. Did you just unplug a NIC and then - after
some time - plug it back in ? For this you don't need your test, you could simply use
org.jgroups.demos.Draw (or ViewDemo)...
I did exactly this, with udp.xml (but loopback="true") and then a
network service stop
After the cluster fell apart, I restarted the network and the cluster merged back into
one. Sometimes 3 singleton clusters merge into 2 first, then into 3, and sometimes they go
straight to 3.
If you did something else, please use Draw or ViewDemo with an XML config, and post exact
steps to reproduce the issue.
viewAccepted is not always reported to all group members
--------------------------------------------------------
Key: JGRP-830
URL:
https://jira.jboss.org/jira/browse/JGRP-830
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.4
Environment: Windows XP
Reporter: cbowditch
Assignee: Vladimir Blagojevic
Fix For: 2.6.5, 2.7
Attachments: JGroups-ViewMergeBug.zip
I have written a test harness application that demonstrates the issue. When there are 3
members in the group, 2 on 1 machine and the third on a second machine not all members of
the group receive a viewAccepted method call everytime a network outage occurs or after a
network outage has been recovered from. I am doing all my testing on Windows XP.
Receiving the viewAccepted method after a network outage or after recovering from a
network outage is vital for all members to be able to keep track of which members are
still present in the group.
I have created a thread on the forum regarding this issue:
http://sourceforge.net/mailarchive/forum.php?thread_name=BAY117-DAV32E556...
Although I have only seen the error reported at the start of that thread once so it may
be a red herring. It may be necessary to break the network connection between the 2
machines in this test 3/4 times as it sometimes works.
If you need anymore information on how to recreate this issue then please let me know and
I will try to assist.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira