[
https://issues.apache.org/jira/browse/CASSANDRA-16376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262934#comment-17262934
]
Josh McKenzie commented on CASSANDRA-16376:
-------------------------------------------
Thanks for the report [~pauliusb]. Someone will take a look and get back with
you; this definitely looks like a blocker to hit RC.
> 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: [email protected]
For additional commands, e-mail: [email protected]
