[
https://issues.apache.org/jira/browse/CASSANDRA-16376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16376:
----------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0-beta5
Since Version: 4.0-beta4
Source Control Link:
https://github.com/apache/cassandra/commit/7e936e7f2c6ccc73d8e3acd31d7050889ec1efbe
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks [~pauliusb] & [~mck], committed to trunk with the nit addressed & the
eclipse warning in `BurnTestUtil` removed.
> 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-beta5
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
