[MB-3669] Tap doesn't handle garbage/new messages that are sent over the same connection Created: 22/Apr/11  Updated: 10/Apr/12  Resolved: 13/Jun/11

Status: Closed
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 1.7 beta
Fix Version/s: 1.7.1
Security Level: Public

Type: Bug Priority: Minor
Reporter: Mike Wiederhold Assignee: Chiyoung Seo
Resolution: Won't Fix Votes: 0
Labels: 1.7.0-release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: CentOS 5.4

Flagged:
Release Note

 Description   
I have a tap client that sends a request for a dump stream. I start receiving the stream and then while the stream is being sent I send another request for a dump stream down the same connection. The result for this action is that my tap stream is terminated. We need to define this scenario better. We can ignore any messages that don't make sense being received and continue the current tap stream. The other option is to just say if the message is garbage ignore it, but if it's a message to start a new tap stream than do that. In any case the tap stream should not be closed.

 Comments   
Comment by Mike Wiederhold [ 13/Jun/11 ]
I talked to Trond recently and the correct behavior is to close a connection if garbage is received.
Generated at Thu Jul 31 06:41:45 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.