Couchbase Server

moxi binary protocol uses 0x82 OOM / ENOMEM error code too much

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.5.3
  • Fix Version/s: 1.7 GA
  • Component/s: moxi
  • Security Level: Public
  • 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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Steve Yen added a comment -
http://review.membase.org/6176
http://review.membase.org/6177
Show
Steve Yen added a comment - http://review.membase.org/6176 http://review.membase.org/6177
Hide
Permalink
Matt Ingenthron added a comment -
Marking for release notes, since this could change the way users expect to error handle.
Show
Matt Ingenthron added a comment - Marking for release notes, since this could change the way users expect to error handle.
Hide
Permalink
Farshid Ghods added a comment -
moxi now will return error # 132 and error #133 instead of converting everything to #134 ( 0x82)
Show
Farshid Ghods added a comment - moxi now will return error # 132 and error #133 instead of converting everything to #134 ( 0x82)

People

  • Assignee:
    Steve Yen
    Reporter:
    Steve Yen
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: