Details
-
Improvement
-
Resolution: Fixed
-
Major
-
1.1.0
-
None
-
None
Description
Add a distinct ResponseStatus for ERR_BUSY, so that some operations that are already a bit unclear in their result don't have further ambiguity when the server is actually busy.
For example, getAndLock and unlock will respond ERR_TEMPFAIL if the object is already locked or when attempting to unlock with wrong CAS. This should be mapped to a CASMismatchException in the client, whereas distinguishable error like ERR_BUSY should be mapped to a TemporaryFailureException.
(see MB-13087)
Attachments
Issue Links
- blocks
-
JCBC-708 In lock-related operations, correctly throw CASMismatchException when receiving TEMPFAIL
- Resolved