ConnectionTable: eagerly verify TCP connection upon lookup ---------------------------------------------------------- Key: JGRP-1067 URL: https://jira.jboss.org/jira/browse/JGRP-1067 Project: JGroups Issue Type: Bug Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.8 Whenever node A sends a message to a node B it looks up a connection from a connection table. In cases connection to B is present in A's table - it is returned to a caller, otherwise a new connection is created. However, the above mentioned connection to B might be closed and not yet removed from A's table (think of a case when B closes connection from its end of the pipe). Therefore, the caller who asked for a connection to B might end up with a stale connection that is guaranteed to throw an exception when A attempts to send a message to B. Of course, JGroups will eventually detect that the message is missing and retransmission will kick in but this situation can be remedied by verifying connection status before returning it to a caller. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira