[
https://issues.jboss.org/browse/JGRP-1252?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1252:
--------------------------------
I think the test may yield incorrect results because to determine the membership, you
parse messages you get via the stdin of a forked child process. However, the might be
garbled input, therefore resulting in incorrect membership...
I did the following:
#1 Start a GossipRouter
#2 Start 4 chat processes
#3 Kill last chat process (number 4)
#4 Kill GR
#5 Start GR
#6 Start 4th chat
#7 Check membership (probe.sh |grep view)
#8 Go back to #3, rinse and repeat 10 times
Step #7 *always* has the correct membership. Sometimes, nodes would show their UUID rather
than their logical names. On the next drawing in the canvas (or a merge, whichever came
first), the logical names would get displayed.
So my manual test does exactly the same as your automatic test, and I could not reproduce
your issue.
I'm going to close this issue again. If you want to, we can have a phone call on this,
but unless you provide me with a test that really shows the issue, I'm not going to
re-open it.
If you want to, we can have a call to dicuss this some more...
TCP Gossip Discovery Issue
--------------------------
Key: JGRP-1252
URL:
https://issues.jboss.org/browse/JGRP-1252
Project: JGroups
Issue Type: Bug
Affects Versions: 2.11
Environment: Windows XP and Solaris 5.10
Reporter: Grahame Rogers
Assignee: Vladimir Blagojevic
Labels: new_and_noteworthy
Fix For: 2.12
Attachments: JGroupsTest.zip, JGroupsTest.zip, JGroupsTest.zip, JGroupsTest.zip,
JGRP-1252-output.txt, JGRP-1252-output2.txt
I run the chat demo app that was shipped with an older version of Jgroups. Using tcp
transport, with tcpgossip for discovery I start up 2 instances of the chat application. I
then restart the gossip server and also another instance of the chat application. The 3rd
instance of the chat application receives a view update (membershipListener.viewAccepted)
only the logical name of one of the 2 previous instances of the chat client is incorrect.
I have detailed the results in:
http://old.nabble.com/TCPGossip-Discovery-Issue-td30227966.html
I will attach the test client to this bug report.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira