[jboss-jira] [JBoss JIRA] Commented: (JGRP-1233) TCPPING fails to connect with different server because sender thread is interrupted too soon?

Bela Ban (JIRA) jira-events at lists.jboss.org
Thu Sep 16 11:38:28 EDT 2010


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

Bela Ban commented on JGRP-1233:
--------------------------------

No, in JGroups the wildcard address 0.0.0.0 doesn't mean anything. 

> TCPPING fails to connect with different server because sender thread is interrupted too soon?
> ---------------------------------------------------------------------------------------------
>
>                 Key: JGRP-1233
>                 URL: https://jira.jboss.org/browse/JGRP-1233
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.10
>            Reporter: Karthik Abram
>            Assignee: Bela Ban
>
> The configuration file I'm using is in the comment below. The log output is below that. The system works just fine if I run two instances of the program on the same machine. However, when I run it on different machines (only 1 port is open between them), I see connection-established, and then I get this in the log:
> TRACE TCPConnectionMap$TCPConnection - TCPConnection.Sender thread terminated at 0.0.0.0:9043
> Looking at the code, it seems the sender thread gets interrupted before it gets data from the other program?
> We cannot using MPING for discovery in our environment and this is a major issue for us. 
> The two machines are 10.0.7.28 and deutergnosis. 10.0.7.28 was started first.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list