Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
Availability - Response Crash
-
Normal
-
Normal
-
User Report
-
All
-
Clients
-
Description
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
Attachments
Attachments
Issue Links
- is duplicated by
-
CASSANDRA-16424 Incorrect stream used in SUPPORTED frame
- Resolved