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

Posted to commits@cassandra.apache.org by "Chris Bannister (JIRA)" <ji...@apache.org> on 2015/02/22 14:20:11 UTC

[jira] [Updated] (CASSANDRA-8848) Protocol exceptions always use streamID 0

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

Chris Bannister updated CASSANDRA-8848:
---------------------------------------
    Attachment: trunk-8848.patch

> Protocol exceptions always use streamID 0
> -----------------------------------------
>
>                 Key: CASSANDRA-8848
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8848
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Chris Bannister
>         Attachments: trunk-8848.patch
>
>
> When decoding the binary protocol if a ProtocolException is thrown the streamID the request came in on is lost. This makes it very hard for drivers to correctly handle improper protocol implementations.
> Included is a test case which sends a frame with version 0x82 and op 0x9 which should return a ProtocolError indicating that PREPARE should be a client Request not a response.



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