[ https://issues.apache.org/jira/browse/CASSANDRA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614627#comment-13614627 ]
Pierre Chalamet commented on CASSANDRA-5164: -------------------------------------------- The patch would be better by inverting lines 202 & 203 in ErrorMessage.java: {code} public static ErrorMessage fromException(Throwable e) ... streamId = ((WrappedException)e).streamId; e = e.getCause(); {code} Otherwise, an invalid cast is raised. Patch enclosed - I've tested it and exception nicely flows to the client using the right stream id. > Invalid streamId in cql binary protocol when using invalid CL > ------------------------------------------------------------- > > Key: CASSANDRA-5164 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5164 > Project: Cassandra > Issue Type: Bug > Components: API > Affects Versions: 1.2.0 > Environment: Windows 8, java version "1.6.0_37" x86 > Reporter: Pierre Chalamet > Assignee: Sylvain Lebresne > Priority: Minor > Fix For: 1.2.4 > > Attachments: 5164-2.txt, 5164.txt > > > Execute a query using invalid CL (0x100 for example) > The response comes but does not use the request streamId (always 0). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira