[
https://jira.jboss.org/jira/browse/JGRP-830?page=com.atlassian.jira.plugi...
]
cbowditch commented on JGRP-830:
--------------------------------
I definitely think this issue has something to do with option AUTO_GETSTATE. When starting
my test App in a slightly different order to above, i.e.
1) Start Member 1 (group Test) on machine A
2) Wait a few seconds until ViewAccepted event has been received
3) Start Member 2 (group Test) on machine A
4) Wait a few seconds until ViewAccepted event has been received
5) Start Member 3 (group Test) on machine B
6) Wait a few seconds until ViewAccepted event has been received
In step 4 no viewAccepted event was received and no setState call was received. However, I
still can't break viewDemo which does not set the option AUTO_GETSTATE. If this is the
case I'm happy to reduce the severity of the bug but I do believe there is still a bug
here.
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