SelectBucketFailedEvent, Unambiguous and Ambiguous Timeout Exceptions with Java SDK


I am getting Unambiguous and Ambiguous Timeout Exceptions after upgrading Java SDK to 3.0.6

I am using below configuration :-

Couchbase server :- Enterprise Edition 6.0.2 build 2413
Spring boot version :- 2.3.2

[][SelectBucketFailedEvent] Select bucket failed with status code 0x1

com.couchbase.client.core.error.AmbiguousTimeoutException: RemoveRequest, Reason: TIMEOUT\n\tat com.couchbase.client.core.msg.BaseRequest.cancel(\n\tat com.couchbase.client.core.Timer.lambda$register$2(\n\tat$HashedWheelTimeout.expire(\n\tat$HashedWheelBucket.expireTimeouts(\n\tat$\n\tat\n\tat\n

com.couchbase.client.core.error.UnambiguousTimeoutException: GetRequest, Reason: TIMEOUT\n\tat com.couchbase.client.core.msg.BaseRequest.cancel(\n\tat com.couchbase.client.core.Timer.lambda$register$2(\n\tat$HashedWheelTimeout.expire(\n\tat$HashedWheelBucket.expireTimeouts(\n\tat$\n\tat\n\tat

can someone give me any pointers for above issues.

i had also checked logs after reading below post, i am not getting any logs like BUCKET_NOT_AVAILABLE.

Thank in advance…

SDK-doctor might be useful -

It might help to see your configuration for couchbase (connection string)
0x1 error code is NOT_FOUND.
Although when I specify an bucket that does not exist I get:

com.couchbase.client.core.error.AuthenticationFailureException: Either the bucket with name “moviesx” is not present or the user does not have the right privileges to access it
at ~[core-io-2.0.5.jar:na]
at ~[core-io-2.0.5.jar:na]
at ~[na:1.8.0_241]

In addition to @mreiche’s point, are you by chance using LDAP authentication or something along those lines?

@amitgupta9501 does your seed node list contain hostnames which do not have the data service enabled ? (so for example only query) - how does your server topology look like?

Thanks for your reply…
bucket name exists, on which application is trying to connect with valid credentials and I can’t see any AuthenticationFailureException also.

Thanks for reply… application is not using any LDAP authentication.