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

Couchbase client stuck indefinitely in constructor

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • 1.2.2
    • 1.1.5
    • Core
    • Security Level: Public
    • Windows, Java app.

    Description

      We recently had some connectivity / responsiveness issues with our Couchbase cluster and we noticed that our automated test suite was stuck for over 12h waiting for CouchbaseClient's constructor to complete, which intern was waiting for channelLatch.await().
      I'm attaching the stack trace of the hanging thread.
      I don't understand the purpose of this latch wait, but perhaps there should be a timeout passed to the await() method, preferably user configurable.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JCBC-368 Deadlock in BucketMonitor.startMonitor() on CountDownLatch when channel creation fails.

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              daschl Michael Nitschinger
              dkarlinsky dmitry karlinsky
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty