Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 4 Oct 2014 14:00:42 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12721610.1402992064000.190640.1412431242869@Atlassian.JIRA>
In-Reply-To: <JIRA.12721610.1402992064000@Atlassian.JIRA>
References: <JIRA.12721610.1402992064000@Atlassian.JIRA>
 <JIRA.12721610.1402992064277@arcas>
Subject: [jira] [Resolved] (CASSANDRA-7406) Reset version when closing
 incoming socket in IncomingTcpConnection should be done atomically
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko resolved CASSANDRA-7406.
------------------------------------------
    Resolution: Duplicate

Resolving as a duplicate of CASSANDRA-7734, for it is essentially about the same thing, and has more linked issues and more comments.

> Reset version when closing incoming socket in IncomingTcpConnection should be done atomically
> ---------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7406
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7406
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: CentOS release 5.5 (Tikanga)
>            Reporter: Ray Chen
>            Assignee: Aleksey Yeschenko
>
> When closing incoming socket, the close() method will call MessagingService.resetVersion(), this behavior may clear version which is set by another thread.  
> This could cause MessagingService.knowsVersion(endpoint) test results as false (expect true here).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)