[jboss-jira] [JBoss JIRA] Commented: (JGRP-1252) TCP Gossip Discovery Issue
[
https://issues.jboss.org/browse/JGRP-1252?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1252:
--------------------------------
OK. Note that if you send a message (e.g. by drawing something in the canvas of Draw, or
sending a chat message), and the physical address of the target(s) is not known, then
JGroups will fetch that information from the GossipRouter. So if you see that the
membership is correct, but some members don't have logical names, you can trigger this
fetch...
In a normal app, this would happen when a message is sent. JGroups does send messages
regularly, e.g. stability or failure detection messages.
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