Uploaded image for project: 'Couchbase Java Client'
  1. Couchbase Java Client
  2. JCBC-117

mention that OperationFuture.get(tmo) changes state when timeout has been reached


    • Type: Improvement
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.3
    • Fix Version/s: .backlog1.x
    • Component/s: Documentation
    • Security Level: Public
    • Labels:


      get(tmo) should not change the underlying state of the command to being timed out. It should simply respond with a TimeoutException but allow the command to continue.

      Specifically, when the arg-tmo (timeout passed as an argument) expires, the underlying command is marked as timed out. For example, if one waits for 50ms on the command and a response has not been received within that time, the command is now dead ('TIMEDOUT', or similar) and waiting again will not help.

      It is understandable that some code might rely on the old behavior, so at the very least, this should be documented in 'BIG RED LETTERS' in the get(tmo) method.

        Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.


          There are no open Gerrit changes for this issue.


            • Assignee:
              daschl Michael Nitschinger
              mnunberg Mark Nunberg
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:

                Gerrit Reviews

                There are no open Gerrit changes