[ https://issues.apache.org/jira/browse/CASSANDRA-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341456#comment-14341456 ]
Chris Bannister commented on CASSANDRA-8848: -------------------------------------------- thanks! > 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 > Assignee: Chris Bannister > Priority: Minor > Fix For: 2.0.13, 2.1.4 > > Attachments: 8848-2.0.txt, 8848-2.1.txt, 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)