[jboss-jira] [JBoss JIRA] Commented: (JGRP-1252) TCP Gossip Discovery Issue

[Grahame Rogers (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577710#comment-12577710 ] 

Grahame Rogers commented on JGRP-1252:
--------------------------------------

Now this is getting very interesting, thanks for these last comments. I reverted back to my original manual test via a chat swing GUI and was able to reproduce in 2.1.12. However, I added a line of code within the message received method where I now call channel.getView and print this out. You are quite correct, I am seeing the scenario where client4 starts up and receives the duff view. I then send a message on any of the clients and when this is received by client4, channel.getView now returns the correct view data. 

The reason I have discovered this issue in the first place is because we are initially looking at adding Jgroups in a way where a GUI shows which nodes are up/down and therefore does not send/receive any application messages. 

Is it possible that my config is just not correct and by configuring stability/FD this problem could be fixed by config? If not, perhaps I could introduce some pragmatic handling where, in the event of me suspecting a duff view, I broadcast a message in order to fix. What do you think? 

> 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