Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 1.1-beta
    • Component/s: None
    • Security Level: Public
    • Labels:
      None

      Description

      The following exceptions are thrown when a CouchbaseClient calls shutdown()

      java.io.IOException: No IO while shut down
      at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:201)
      at com.couchbase.client.CouchbaseConnection.run(CouchbaseConnection.java:230)

      This can easily be seen when logging is enabled.

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

        Activity

        Hide
        daschl Michael Nitschinger added a comment -

        In general, this kind of exception thrown during shutdown is fine and is only logged in debug mode.

        Matt, I see two options here:

        • Leave it as is, the exception is only logged as debug.
        • we wrap the run() loop currently with if(!reconfiguring), maybe wen can also add && !shutDown? Or does this infer with the shutdown procedure?

        Thanks,
        Michael

        Show
        daschl Michael Nitschinger added a comment - In general, this kind of exception thrown during shutdown is fine and is only logged in debug mode. Matt, I see two options here: Leave it as is, the exception is only logged as debug. we wrap the run() loop currently with if(!reconfiguring), maybe wen can also add && !shutDown? Or does this infer with the shutdown procedure? Thanks, Michael
        Hide
        ingenthr Matt Ingenthron added a comment -

        I think the current behavior is correct. We want our IO thread to not do any new IO while shutting down. Someone called shutdown either immediate, or with a time value and there was more IO to be done, so we're logging that we're not doing it.

        Show
        ingenthr Matt Ingenthron added a comment - I think the current behavior is correct. We want our IO thread to not do any new IO while shutting down. Someone called shutdown either immediate, or with a time value and there was more IO to be done, so we're logging that we're not doing it.
        Hide
        daschl Michael Nitschinger added a comment -

        I'm closing this after discussion that the current behavior is correct.

        IO during shutdown is not accepted but the log message should do no harm in that case. Thats why its printed as debug and not as a warning.

        Show
        daschl Michael Nitschinger added a comment - I'm closing this after discussion that the current behavior is correct. IO during shutdown is not accepted but the log message should do no harm in that case. Thats why its printed as debug and not as a warning.

          People

          • Assignee:
            daschl Michael Nitschinger
            Reporter:
            james.mauss James Mauss
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes