Details
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
-
JCBC-368 Deadlock in BucketMonitor.startMonitor() on CountDownLatch when channel creation fails.
- Resolved