[jboss-jira] [JBoss JIRA] Commented: (JGRP-1252) TCP Gossip Discovery Issue
[
https://jira.jboss.org/browse/JGRP-1252?page=com.atlassian.jira.plugin.sy...
]
Grahame Rogers commented on JGRP-1252:
--------------------------------------
Hi,
So you set the bind_addr parameter when you ran GR? I usually just run the GR with all the
default values - maybe if I set the GR up as you have the issue that I was easily able to
reproduce would go away. Can you explain the process you went through when configuring the
bind_addr on the GR, not sure how you decide which NIC to configure to, then I can do the
same and see if the problem persists
TCP Gossip Discovery Issue
--------------------------
Key: JGRP-1252
URL: https://jira.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, 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