I am having a connectivity issue that is fancy in virtual virtual vpc on Amazon (AWS). My context is this: I have a subnet on this subnet. I have 2 client machine machines where I used the Couchbase java SDK and the machine for the Couchbase server. Both are large specimens. The current version of java 1.6. I opened all the required ports (8091,8092,11210) for Couchbase in the security groups. I am checking the connection with the curl command to check the connection to the bucket and no problem here. Strange behavior - when I try to access a view using a java client, because I get a timeout error, although the java client has been authenticated successfully.
This is what my magazine looks like:
(CacheManager.java:102) -B06C9F5CFF85- Cache client checked out [stdout]
INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/10.0.X.XXX:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@57a220c2
INFO net.spy.memcached.auth.AuthThread: Authenticated to 10.0.X.XXX/10.0.X.XXX:11210
Added 10.0.X.XXX to connect queue
INFO com.couchbase.client.CouchbaseClient: viewmode property isn't defined. Setting viewmode to production mode
INFO com.couchbase.client.http.AsyncConnectionManager: Opening new Couchbase HTTP connection
INFO com.couchbase.client.http.AsyncConnectionManager$ConnRequestCallback: /10.0.X.XXX:8092 - Session request successful
ERROR com.couchbase.client.ViewNode$EventLogger: Connection timed out: [10.0.X.XXX/10.0.X.XXX:8092]
and then after a while
INFO com.couchbase.client.ViewConnection: Node 10.0.X.XXX has no ops in the queue
INFO com.couchbase.client.ViewNode: I/O reactor terminated for 10.0.X.XXX
SHUTTING DOWN (informed client)) INFO com.couchbase.client.CouchbaseConnection: Shut down Couchbase client
, - , .
:
Couchbase 2.0
Java 1.6
Ubuntu 11.10 x64
Couchbase, vm lan, .
- . Couchbase , .
.