Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.4.4
-
None
-
Security Level: Public
-
None
-
couchbase-server-community_x86_64_2.2.0 (AWS AMI) / java couchbase-client.version 1.4.4
Description
We are having an issue running only on production (we can't reproduce this issue on our local environments), and basically it is that, when because an external reason our backend loses connection with the couchbase cluster, then it never reconnects again.
The only way we found to reproduce this issue was:
1. Run the application, with the couchbase instance running as well,
2. When everything it's okay, then shutdown the couchbase process,
3. Try to perform some action on the system, which will fail, because the connection was lost,
4. Run again the couchbase server,
5. The expected behavior should be, to detect again the running instance and reconnect, however if we what this to happen, we have to restart our application server.
Questions:
- Should we implement some kind of mechanism to provide reconnection? How can we implement this? Do you have some kind of guide?
- We also know there was release a newer version of the java sdk (2.0), do you know if this issue was solved?
Appendix:
The exception we are receiving when we lost connection is:
» 05:08:22.090 at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:98)
|
» 05:08:22.090 at org.eclipse.jetty.server.Server.handle(Server.java:461)
|
» 05:08:22.090 at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:284)
|
» 05:08:22.090 at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
|
» 05:08:22.090 at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:534)
|
» 05:08:22.090 at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
|
» 05:08:22.090 at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
|
» 05:08:22.090 at java.lang.Thread.run(Thread.java:745)
|
» 05:08:22.090 Caused by: net.spy.memcached.internal.CheckedOperationTimeoutException: Operation timed out. - failing nodes: [OUR_AWS_NODES] Exception
|
» 05:08:22.090 at net.spy.memcached.internal.BulkGetFuture.get(BulkGetFuture.java:127)
|
» 05:08:22.090 at net.spy.memcached.internal.BulkGetFuture.get(BulkGetFuture.java:52)
|
» 05:08:22.090 at com.couchbase.client.internal.ViewFuture.get(ViewFuture.java:72)
|
» 05:08:22.090 at com.couchbase.client.internal.ViewFuture.get(ViewFuture.java:50)
|
» 05:08:22.090 at com.couchbase.client.internal.HttpFuture.get(HttpFuture.java:72)
|
» 05:08:22.090 ... 63 more
|
» 05:08:22.291 2014-10-30 04:08:22 ERROR GeneralExceptionMapperProvider:22 - [OUR_AWS_IP] Timed out waiting for operation
|
Thanks