[
https://jira.jboss.org/browse/JGRP-1233?page=com.atlassian.jira.plugin.sy...
]
Karthik Abram edited comment on JGRP-1233 at 9/17/10 12:06 PM:
---------------------------------------------------------------
Thanks for your prompt help with this.
was (Author: karthik2):
When you say that 0.0.0.0 is invalid in jgroups, I take it you are referring to
interface handling withing jgroups. Because in terms of TCP, binding on 0.0.0.0 shows
connections being established and data traveling through them.
Thanks for your prompt help with this.
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