cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-5438) possibly wrong stream id when cassandra reports an error
Date Mon, 08 Apr 2013 13:45:34 GMT


Sylvain Lebresne resolved CASSANDRA-5438.

    Resolution: Duplicate

I highly suspect this has been fixed by CASSANDRA-5164. You can try against the current 1.2
tip if you want, but otherwise 1.2.4 should hopefully be out soonish. Of course, if CASSANDRA-5164
doesn't fix it, feel free to re-open.
> possibly wrong stream id when cassandra reports an error
> --------------------------------------------------------
>                 Key: CASSANDRA-5438
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.3
>         Environment: Linux x86_64
>            Reporter: Sorin Manolache
> I use the binary protocol. I send a correct prepare request on stream 6 (packets 7 and
9 in the attached pcap). Then I send a malformed execute request on stream 7 (packets 13 and
15). The server responds with an error response (packet 17). The stream id field of the response
contains 0. Shouldn't it contain 7, the id of the execute request?
> The pcap file is here:

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:

View raw message