[
https://issues.apache.org/jira/browse/CASSANDRA-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16424:
----------------------------------------
Resolution: Duplicate
Status: Resolved (was: Triage Needed)
Thanks [~martin-sucha], this was fixed in CASSANDRA-16376 and will be included
in 4.0.0-beta5 (though it's committed to trunk now if you want to verify
against a local build).
> Incorrect stream used in SUPPORTED frame
> ----------------------------------------
>
> Key: CASSANDRA-16424
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16424
> Project: Cassandra
> Issue Type: Bug
> Reporter: Martin Sucha
> Priority: Normal
> Attachments: cassandra4beta4.pcapng.gz, reproducer.zip
>
>
> Cassandra 4.0 beta4 does not correctly send replies to OPTIONS frames when
> using CQL protocol version 4: In response to OPTIONS frame sent with stream
> ID 1, Cassandra 4.0 beta4 replies with SUPPORTED frame with stream ID 0
> (instead of replying with the same stream ID as client requested).
> See attached network dump.
> The issue can be reproduced by connecting with gocql driver, see attached Go
> program.
> Happens also when using protocol version 3. I haven't checked protocol
> version 5 as we don't have support for it in gocql yet.
> The issue cannot be reproduced with Cassandra 4.0 beta3.
> Originally reported at gocql: https://github.com/gocql/gocql/issues/1532
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
