You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on the test of my application with CouchbaseMock in the following context: CouchbaseMock 1.5.25 and Couchbase Java SDK is 3.0.10.
Establishing a connection to the bucket, for every transaction (different from an upsert) the mock engine give me the following errors in console:
java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 10000ms in 'source(MonoDefer)' (and no fallback has been configured)
The timeout of 10s occurs in every request (as a WARNING) except upsert.
For every operation, for instance count, I get a FeatureNotAvailableException:
com.couchbase.client.core.error.FeatureNotAvailableException: The cluster does not support cluster-level queries (only Couchbase Server 6.5 and later) and no bucket is open. If an older Couchbase Server version is used, at least one bucket needs to be opened to dispatch this query request!
at com.couchbase.client.core.error.FeatureNotAvailableException.clusterLevelQuery(FeatureNotAvailableException.java:41)
Doing the same test with the previous Couchbase version, everything works fine.
Is there any way to mock the new SDK?
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
I'm currently working on the test of my application with CouchbaseMock in the following context: CouchbaseMock 1.5.25 and Couchbase Java SDK is 3.0.10.
Establishing a connection to the bucket, for every transaction (different from an upsert) the mock engine give me the following errors in console:
The timeout of 10s occurs in every request (as a WARNING) except upsert.
For every operation, for instance count, I get a FeatureNotAvailableException:
Doing the same test with the previous Couchbase version, everything works fine.
Is there any way to mock the new SDK?
Thanks
The text was updated successfully, but these errors were encountered: