You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Shawn Kumar (JIRA)" <ji...@apache.org> on 2014/09/23 00:44:34 UTC

[jira] [Commented] (CASSANDRA-7406) Reset version when closing incoming socket in IncomingTcpConnection should be done atomically

    [ https://issues.apache.org/jira/browse/CASSANDRA-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143972#comment-14143972 ] 

Shawn Kumar commented on CASSANDRA-7406:
----------------------------------------

Looks like this particular issue was also brought up and is being looked at in 7734. It would be greatly appreciated if you could note the version you noticed this in. 

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