[RxComputationScheduler-1] Endpoint - [][KeyValueEndpoint]: Socket connect took longer than specified timeout

Couchbase 4.6 and Java SDK 2.5.8 /2.5.6/2.5.5

CouchbaseEnvironment env = DefaultCouchbaseEnvironment.builder().connectTimeout(100000)

Getting below message while trying to open bucket …

[RxComputationScheduler-1] Endpoint - [][KeyValueEndpoint]: Socket connect took longer than specified timeout…

and followed by this

Endpoint - Error during reconnect: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: Connect callback did not return, hit safeguarding timeout.

socketConnectTimeout does control the timeout in question, but the default should be fine. Do you have the required ports open? https://developer.couchbase.com/documentation/server/current/install/install-ports.html Can you connect using the command line tools? https://developer.couchbase.com/documentation/server/current/sdk/webui-cli-access.html

Thank you for the reply .
Would able to open bucket by using 2.2.0-dp and not with later versions .
Also i have a test application which is connecting to same couch with all latest versions.
Is there any dependency ?

So you have an app that’s on the latest Java client that connects to your Couchbase Server fine, and then another app that can only connect to the same server if you’re using Java client 2.2.0-dp and no later - is that all correct?

What differences are there between the non-working and working apps? Running on different machines with different network access? Different firewall config? Different /etc/hosts? Do the CLI tools work from the machine the non-working app is on?

You could try using Wireshark to capture the network traffic. It will show if you’re getting any packets back from the server at all.

Both applications (Test app and multi layered application ) are running on the same Machine .
Couchbase also installed on the same Machine.