you could try to silence it and check if it is indeed the keepAlive that causes this problem (which looks very weird to me btw) by deactivating keep alive:
- Create a static
CouchbaseEnvironment
- Set
keepAliveInterval
to 0 - Use the environment in the
Cluster
creation
In your example:
CouchbaseEnvironment env = DefaultCouchbaseEnvironment.builder()
.keepAliveInterval(0)
.build();
public class Persistence {
//Configuration
public static String clusterAddress = "192.168.0.55";
public static String bucketName = "default";
public static String bucketPassword = null;
public static final CouchbaseEnvironment env = DefaultCouchbaseEnvironment.builder()
.keepAliveInterval(0).build();
public static Cluster cluster;
public static Bucket bucket;
public static Bucket getBucketInstance() {
if (cluster == null) {
cluster = CouchbaseCluster.create(env, clusterAddress);
}
if (bucket == null) {
bucket = cluster.openBucket(bucketName, bucketPassword);
}
return bucket;
}
}
This should deactivate keep alives and you can then confirm that the messages have gone away.