[jboss-jira] [JBoss JIRA] Commented: (JGRP-1252) TCP Gossip Discovery Issue
[
https://issues.jboss.org/browse/JGRP-1252?page=com.atlassian.jira.plugin....
]
Grahame Rogers commented on JGRP-1252:
--------------------------------------
Hi,
I have written a test class called ChatTestManager attached in JgroupsTest.zip, which
encapsulates the problem I originally reported. In short, this starts a GR, then 4
clients. It then kills 1 client, then restarts the GR and adds another client. At this
point the issue should be replicated and will log out a report. I have noticed that
sometimes the new client fails to start properly so the test sometimes incorrectly logs
failure, but this is obvious as one of the members logged will be shown as null. This
project should be self contained, so you just need to unzip and call run.bat. Please note
that this needs to be run on a network and not stand-alone. The class is fully commented
but if you have any questions, please shout
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.11.1, 2.12
Attachments: 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