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
Perry Krug made changes -
Field Original Value New Value
Component/s moxi [ 10020 ]
Perry Krug made changes -
Affects Version/s 1.6.5.3 [ 10146 ]
Perry Krug made changes -
Assignee Steve Yen [ steve ]
Steve Yen made changes -
Assignee Steve Yen [ steve ]
Steve Yen made changes -
Summary moxi binary protocol uses 0x82 OOM error code too much moxi binary protocol uses 0x82 OOM / ENOMEM error code too much
Steve Yen made changes -
Comment [ http://review.membase.org/6176
http://review.membase.org/6177
]
Steve Yen made changes -
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Matt Ingenthron made changes -
Flagged [Release Note]
Farshid Ghods made changes -
Fix Version/s 1.7 GA [ 10111 ]
Farshid Ghods made changes -
Labels 1.7.0-release-notes

People

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

Dates

  • Created:
    Updated:
    Resolved: