[
https://issues.apache.org/jira/browse/CASSANDRA-16376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16376:
----------------------------------------
Authors: Sam Tunnicliffe
Test and Documentation Plan: Added unit test covering all supported
protocol versions.
Status: Patch Available (was: Open)
The fix is really trivial, just an oversight in the handler which takes care of
initial protocol negotiation. I've added a unit test which checks the stream
ids across the negotiation process for all supported versions.
[~pauliusb] if you're able to test with a dev build, please give it a try &
thanks for the report.
||branch||Circle CI|Apache CI|
|[16376-trunk|https://github.com/beobal/cassandra/tree/16376-trunk]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16376-trunk]|[apache|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/283]|
> Response headers to OPTION messages always have Stream ID of zero
> ------------------------------------------------------------------
>
> Key: CASSANDRA-16376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16376
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Paulius Bankauskas
> Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: cass-dump.pcap
>
>
> It seems that streaming behavior has changed since version 4.0-beta2. When a
> new connection is made, all responses to the OPTIONS messages always return
> with stream id 0 even if requests are made with stream id 1. This causes
> connection failures on some clients.
> Attached wireshark dump with an example.
>
> Node version: 4.0-beta4
> Native protocol version: tested with v3 and v4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
