[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=12572213#comment-12572213 ] 

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

Hi,
I think I have got to the bottom of why my test scenario is failing, I just need to make sure the same issue is true of my real project, but here's what I found. In my test app, when the gossip router is shut down, the RouterStubManager attempts to reconnect (startReconnecting). What I found was when this connection attempt fails, an exception is caught within this method and a warning is logged. However, the call to the logger never returns in this scenario, it just gets stuck. I dug a bit deeper and noticed that my test app does not have log4j on the classpath, so the JDKLogImpl is being used and if I add log4j the problem seems to go away (not fully tested yet). The weird thing is that the logging is generally fine and only goes wrong when startReconnecting comes into play. Therefore to reproduce, just make sure log4j is not on the classpath, hope this helps.

> 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, 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