[MB-3479] moxi binary protocol uses 0x82 OOM / ENOMEM error code too much Created: 02/Mar/11 Updated: 04/Jun/11 Resolved: 12/May/11 |
|
| Status: | Resolved |
| Project: | Couchbase Server |
| Component/s: | moxi |
| Affects Version/s: | 1.6.5.3 |
| Fix Version/s: | 1.7 GA |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Steve Yen | Assignee: | Steve Yen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 1.7.0-release-notes | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Flagged: |
Release Note
|
| Description |
|
In binary client-side protocol, moxi maps too many error conditions to 0x82, the "out-of-memory" binary response status code. That is, moxi is treating 0x82 incorrectly and confusingly too much like a catch-all SERVER_ERROR kind of response code.
|
| Comments |
| Comment by Steve Yen [ 12/May/11 ] |
|
http://review.membase.org/6176
http://review.membase.org/6177 |
| Comment by Matt Ingenthron [ 13/May/11 ] |
| Marking for release notes, since this could change the way users expect to error handle. |
| Comment by Farshid Ghods [ 04/Jun/11 ] |
| moxi now will return error # 132 and error #133 instead of converting everything to #134 ( 0x82) |