Couchbase

[JCBC-278] ConnectionFactoryBuilder has wrong default settings

Wed, 3 Apr 2013 13:09:33 -0500

The Builder uses wrong failure mode and default hash, they differ from instantiating the factory directly. This causes inconsistencies and also EPT node failures not to be detected properly.

[JCBC-261] Warmup Backoff breaks Memcache Buckets

Tue, 12 Mar 2013 06:22:04 -0500

A recent change regarding warmup backoff breaks compat with memcache type buckets.

[JCBC-251] Observe ignores replica on index 0

Wed, 27 Feb 2013 13:39:37 -0600

A replica on index 0 is not added to the broadcast observe list and therefore leads to timeouts when persistence constraints are provided.

[JCBC-245] Docs: Javadoc states that a java.lang.String is required for the value in a write operation, whereas online docs state object

Wed, 27 Feb 2013 13:47:44 -0600

Java docs here: http://www.couchbase.com/autodocs/couchbase-java-client-1.1.2/

All set/replace/add/cas operations state something like:
cas(java.lang.String key, long cas, java.lang.String value, PersistTo req)

Whereas the docs here: http://www.couchbase.com/docs/couchbase-sdk-java-1.1/api-reference-summary.html

State that it's an "Object value"

Looking deeper, it appears that the memcached methods inherited from spy use java.lang.object which leads to user confusion when trying to compare the two.

[JCBC-242] The flush() operations always fails with "401 Unathorized" message

Duplicate — Fri, 8 Feb 2013 10:10:20 -0600

The flush operations seems to require some kind of authorization, however the client library does not provide a way to do it.

The documentation is does not mention anything about this.

Is there a magical way I can call flush?
I attached the source code which reproduces the problem.

[JCBC-219] Fix reconnect logic when server closes the socket.

Tue, 29 Jan 2013 01:32:40 -0600

When the server disconnects on us during a valid remove/failover rebalance, it is the case that the CouchbaseClient stays connected and doesnt try to disconnect and retry. This leaves the client in a dangerous state where no updates are fetched and therefore the map is incorrect.

[JCBC-168] CouchClient.getView always throws an exception

Tue, 11 Dec 2012 10:16:53 -0600

It would seem that client.getView(String designdocName, String viewName) has stopped working in 1.1-beta. It now throws:

java.lang.RuntimeException: Timed out waiting for operation
at com.couchbase.client.internal.HttpFuture.get(HttpFuture.java:66)
at com.couchbase.client.CouchbaseClient.getView(CouchbaseClient.java:492)

This was working fine in 1.1-dp4.

[JCBC-162] re-enable delete observe against 2.0 server

Mon, 3 Dec 2012 14:30:52 -0600

At one point, the observe delete had been disabled on the master branch owing to changes in approach and needing to get a change merged for delete. Once this is complete, we need to revert the change.

See the review for the remove here: http://review.couchbase.org/20918

[JCBC-160] merge in changes from the release10 branch for 1.1beta

Mon, 3 Dec 2012 12:34:32 -0600

In particular, the fix for ~~JCBC-70~~ is needed, but there are a couple of changes which need to be merged in

[JCBC-158] add a debug=true option to view query options

Mon, 3 Dec 2012 01:38:08 -0600

To be able to diagnose issues that may come up with views, please add a debug=true query parameter. Optionally, we could add a cbclient.properties parameter to be able to turn on view debugging (for all view requests or just some that match a regex?) without code changes (though, with restarts).

[JCBC-154] merge in changes from the release11c branch

Mon, 3 Dec 2012 12:34:05 -0600

When reviewing some changes on the "c" branch, I happened to notice there may be one change that hasn't been submodule merged

Upon further inspection, it looks like a few other changes haven't been merged either. We'll need to merge this branch back in.

[JCBC-153] Raise view timeout from 60s to 75s

Mon, 3 Dec 2012 05:36:19 -0600

Since the server side view timeout is 60s, we should raise the client side a bit higher. 75s seems like the right number. It should be tuneable though.

[JCBC-150] "Failed to access the view" error when querying a view with reduce

Tue, 27 Nov 2012 09:30:15 -0600

Attempting to make a call to CouchbaseClient.query(view, query) with a view that has a reduce (even just "_count") results in the following exception when results are returned:

java.lang.RuntimeException: Failed to access the view
at com.couchbase.client.CouchbaseClient.query(CouchbaseClient.java:634)

Worth noting:
- If the query returns no results (ViewResponse.size() returns 0), you do not get the exception...
- If the reduce method is removed from the view, everything works fine. However, using query.setReduce(false) does not work.

[JCBC-147] Rename getViews() to getDesignDocument()

Dependency — Mon, 3 Dec 2012 13:39:32 -0600

The getViews() method should be renamed to getDesignDocument() before the API is stable. This is also in preparation for the createDesignDocument() and deleteDesignDocument() additions.

[JCBC-144] flush command needs to use RESTful flush for Couchbase Buckets

Tue, 11 Dec 2012 01:05:09 -0600

The current flush command needs to be connected to the RESTful flush.

[JCBC-110] observe method does not correctly check persistence or replication status on replica node/vbuckets

Sun, 16 Sep 2012 18:31:06 -0500

When performing some additional testing, Abhinav noticed some unusual behavior in interacting with clients. After checking with Mike a bit, they noticed that observe protocol were not going to replica node/vbuckets during the poll interval loop.

[JCBC-70] Client fails to reconnect to server of non-default memcached bucket after failover and add back

Dependency — Wed, 30 Jan 2013 04:01:25 -0600

In earlier tests with reconnecting to a node on failover we used default memcached bucket. But when we tested the same scenario with a non-default bucket, we noticed the client did not reconnect (due to a null pointer exception internally). I have attached the SDK logs for this scenario where we used "IndexByLniataData" memcached bucket. The problem presents when adding the node back after a failover.

11:34:43,411 DEBUG [Memcached IO over {MemcachedConnection to /10.14.5.119:11210}] [CouchbaseMemcachedConnection] Selecting with delay of 3038ms
Exception in thread "Thread-3" java.lang.NullPointerException
        at net.spy.memcached.auth.AuthThread.buildOperation(AuthThread.java:117)
        at net.spy.memcached.auth.AuthThread.run(AuthThread.java:86)

Logs/stack trace attached.

[JCBC-63] add APIs for creating and deleting design documents for CBS 2.0

Dependency — Thu, 29 Nov 2012 02:58:04 -0600

There are have been several requests from users to have APIs to create and delete views from the Java (and other) SDKs.
This is a MUST have for some customers and needs to be a part of the Client SDK we release prior to Beta.

[JCBC-47] Query.copy does not copy includeDocs property

Fri, 1 Jun 2012 19:11:58 -0500

Query.java line 200 in function copy():
setIncludeDocs(willIncludeDocs());

Should be
query.setIncludeDocs(willIncludeDocs());

Paginated queries depend on copy() so paginatedQuery requiring the document fail with:
java.lang.UnsupportedOperationException: This view result doesn't contain documents

[JCBC-40] paginatedQuery throws NoSuchElementException and NPE

Mon, 3 Dec 2012 05:36:19 -0600

view iteration is incomplete and throws exceptions for
groovy code:
paginator = client.paginatedQuery(view, query, n)
while (paginator.hasNext()) {
  row = paginator.next() // Exception on this line
  ...
}

java.util.NoSuchElementException
        at java.util.LinkedList$ListItr.next(LinkedList.java:698)
        at com.couchbase.client.protocol.views.Paginator.next(Paginator.java:76)
        at com.couchbase.client.protocol.views.Paginator.next(Paginator.java:35)
        at java_util_Iterator$next.call(Unknown Source)

AND

java.lang.NullPointerException
        at com.couchbase.client.protocol.views.Paginator.getNextPage(Paginator.java:93)
        at com.couchbase.client.protocol.views.Paginator.hasNext(Paginator.java:67)
        at java_util_Iterator$hasNext.call(Unknown Source)

Paginator also has a couple odd returns
1) next() can return null, but it should never return null unless lastRow is null. I don't think lastRow should ever be null.
2) getNextPage() has a return type, HttpFuture<ViewResponse>, but always returns null

[JCBC-35] Exception during reconfiguring of client

Tue, 26 Mar 2013 07:02:38 -0500

Multiple different stackstraces below also see the following right before it starts to fail:

"Node exepcted to receive data is inactive. This could be due to afailure within the cluster. Will check for updated configuration. Key without a configured node is: akey12324234"

Then it's fails a number of times and

Failed to reconfigure client, staying with previous configuration.
java.lang.IllegalArgumentException: TODO: refactor this
        at com.couchbase.client.vbucket.config.CacheConfig.getVbucketsCount(CacheConfig.java:55)
        at com.couchbase.client.vbucket.config.DefaultConfig.compareTo(DefaultConfig.java:145)
        at com.couchbase.client.vbucket.VBucketNodeLocator.updateLocator(VBucketNodeLocator.java:133)
        at com.couchbase.client.CouchbaseConnection.reconfigure(CouchbaseConnection.java:120)
        at com.couchbase.client.CouchbaseClient.reconfigure(CouchbaseClient.java:176)
        at com.couchbase.client.vbucket.ReconfigurableObserver.update(ReconfigurableObserver.java:54)
        at java.util.Observable.notifyObservers(Observable.java:142)
        at com.couchbase.client.vbucket.BucketMonitor.setBucket(BucketMonitor.java:257)
        at com.couchbase.client.vbucket.BucketMonitor.startMonitor(BucketMonitor.java:187)
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.subscribe(ConfigurationProviderHTTP.java:243)
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.finishResubscribe(ConfigurationProviderHTTP.java:215)
        at com.couchbase.client.CouchbaseConnectionFactory.checkConfigUpdate(CouchbaseConnectionFactory.java:182)
        at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:165)
        at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
        at net.spy.memcached.MemcachedClient.asyncGet(MemcachedClient.java:835)
        at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:997)

Failed to reconfigure client, staying with previous configuration.
java.lang.IllegalArgumentException: TODO: refactor this
        at com.couchbase.client.vbucket.config.CacheConfig.getVbucketsCount(CacheConfig.java:55)
        at com.couchbase.client.vbucket.config.DefaultConfig.compareTo(DefaultConfig.java:145)
        at com.couchbase.client.vbucket.VBucketNodeLocator.updateLocator(VBucketNodeLocator.java:133)
        at com.couchbase.client.CouchbaseConnection.reconfigure(CouchbaseConnection.java:120)
        at com.couchbase.client.CouchbaseClient.reconfigure(CouchbaseClient.java:176)
        at com.couchbase.client.vbucket.ReconfigurableObserver.update(ReconfigurableObserver.java:54)
        at java.util.Observable.notifyObservers(Observable.java:142)
        at com.couchbase.client.vbucket.BucketMonitor.setBucket(BucketMonitor.java:257)
        at com.couchbase.client.vbucket.BucketMonitor.replaceConfig(BucketMonitor.java:307)
        at com.couchbase.client.vbucket.BucketUpdateResponseHandler.messageReceived(BucketUpdateResponseHandler.java:81)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
        at com.couchbase.client.vbucket.BucketUpdateResponseHandler.handleUpstream(BucketUpdateResponseHandler.java:194)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:513)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:497)
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:434)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340)
        at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192)
        at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
        at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)

[JCBC-27] race condition during startup

Mon, 4 Mar 2013 08:59:49 -0600

During startup, if there is no authentication (and thus no authentication latch) we can reply with errors before we get the configuration back and settled in with the node locator. This should be more reliable.

[JCBC-21] Move the view code into CouchbaseClient

Wed, 21 Mar 2012 00:06:13 -0500

Move the view code into CouchbaseClient

[JCBC-20] CouchbaseClient instances consume all CPU resources

Fri, 29 Jun 2012 14:28:12 -0500

When creating one or more CouchbaseClient instances, each one appears to consume 100% of the available CPU resources per core, at least on machines I've tested.
Test case (eclipse project and ant build) included.
Also included a snapshot of my system graph on my dev machine while running the included test.

[JCBC-241] Paginator object doesn't move onto next "page" correctly

Dependency — Wed, 8 May 2013 05:25:14 -0500

Customer found his own issue:
I had a look at the source code for the java driver and found the error there. It is in:

com.couchbase.client.protocol.views.Paginator.getNextPage()

Right after calculating the number of "remaining" keys, it sets the limit of the query to the remaining number of keys and re-runs the query. What is missing here is:

q.setSkip(totalDocs);

To actually start from the entry after the last entry on the current page. I have tried this and it works. But there is more code in this method and it is not very easy to follow so important to make sure that this fits.

I am enclosing a diff.

[JCBC-272] removing non-bootstrap node with memcached bucket okay, but adding the same node results in failures

Duplicate — Fri, 15 Mar 2013 03:28:33 -0500

From the attached log, one will see first the removal of a node (click remove -> click rebalance), and things are generally okay.

Following that, you'll see the node added (via the config wizard, joining to node 192.168.1.200), and one configuration received, but nothing actually used yet.

Following that, you'll see the node rebalanced in with a set of assertion errors and then workload ceases.

Notably:
2013-03-13 19:29:03.924 INFO com.couchbase.client.CouchbaseMemcachedConnection: Reconnecting {QA sa=/192.168.1.201:11210, #Rops=1, #Wops=0, #iq=0, topRop=Cmd: 0 Opaque: 139891 Key: pool-25-thread-1:48454, topWop=null, toWrite=0, interested=1}
Exception in thread "Memcached IO over {MemcachedConnection to /192.168.1.200:11210 /192.168.1.202:11210 /192.168.1.201:11210}" java.lang.AssertionError: Attempting to overwrite channel

[JCBC-271] Adding a node to an existing cluster causes issues with a running memcached bucket

Duplicate — Sat, 16 Mar 2013 02:36:33 -0500

When adding a node to a cluster, I'd observed a number of AssertionErrors and some very odd errors about connections being null.

This popped up when I wasn't expecting an issue, so I'm a bit surprised. The scenario I think is:

Steps to reproduce:
1. Have two nodes running (.200 and .201 in my case here)
2. Add another node (.202 in my case here)

See the logs for what detail is available.

[JCBC-230] View Connection only released when successful (not on failure)

Wed, 6 Feb 2013 01:50:09 -0600

When a view operation is cancelled (timeout or else), the underlying connection for the ConnectionManager is not released and as a result no new view request can go over it.

[JCBC-227] client behaves poorly if entire URI list is not available

Fri, 1 Feb 2013 02:52:04 -0600

Currently, if the client has no valid URIs in it's list, it's reported that it will spin trying to connect nonstop. We should add a backoff if the entire list is traversed and unavailable. An exponential backoff (do-while style) with a ceiling and warning to a log is probably best.

[JCBC-198] Using ReplicateTo.ONE after node-failover leads to index out of bounds

Wed, 27 Feb 2013 13:46:03 -0600

using couchbase client library version 1.1.0, server version 2.0.0 community edition (build-1976-rel).
The cluster configuration remains same as in my initial email - three servers with "Enable Failover" property ON, a dedicated port "couchbase" bucket with 1 replica enabled.

When stopping a server the client fails to communicate with the cluster with several errors.

Client initializing -

List<URI> serverList = parseConnectionProperties(port, hosts);
CouchbaseConnectionFactory cf = new CouchbaseConnectionFactory(serverList, cacheName, "");
client = new CouchbaseClient(cf);

Usage of the client to write data -

public void put(final String key, final String value) {
client.set(key, expirationSeconds, value, PersistTo.MASTER, ReplicateTo.ONE);
}

During the tests, when cluster is not available, I did a thread dump to the application , see the print below (ajp--127.0.0.1-8020-1@8796). Is it possible that node that is down is in some way a "master" of the data, and since the client.set() method uses PersistTo.MASTER parameter the things do not work?

"ajp--127.0.0.1-8020-1@8796" daemon prio=5 tid=0x8c nid=NA waiting
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Unsafe.java:-1)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
at com.couchbase.client.CouchbaseClient.observe(CouchbaseClient.java:1650)
at com.couchbase.client.CouchbaseClient.observePoll(CouchbaseClient.java:1750)
at com.couchbase.client.CouchbaseClient.set(CouchbaseClient.java:1199)
at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.put(CouchbaseReadWriteCache.java:40)
at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.put(CouchbaseReadWriteCache.java:17)
at com.liveperson.liveEngage.cache.LEUsersCacheManager.setSessionDataCache(LEUsersCacheManager.java:121)
at com.liveperson.liveEngage.ssoIdpLogin.LoginVerification.writeLoginDataToJbossCache(LoginVerification.java:246)
at com.liveperson.liveEngage.ssoIdpLogin.LoginVerification.verifySsoLogin(LoginVerification.java:87)
at com.liveperson.liveEngage.filters.AuthFilter.doFilter(AuthFilter.java:71)
at com.liveperson.liveengage.authentication.filters.AuthenticationByProtocolFilter.doFilter(AuthenticationByProtocolFilter.java:71)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at com.liveperson.liveEngage.filters.CommonFilter.doFilter(CommonFilter.java:35)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at org.jboss.as.web.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:125)
at org.jboss.as.web.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91)
at org.jboss.as.web.session.JvmRouteValve.invoke(JvmRouteValve.java:88)
at org.jboss.as.web.session.LockingValve.invoke(LockingValve.java:56)
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:490)
at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:480)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039)
at java.lang.Thread.run(Thread.java:722)

The errors i get during the test after a server was failed over -

17:45:41,911 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) [ERROR] [ajp--127.0.0.1-8020-4] Verify Sso Login failed. sessionId - n2b+0EZEzTaM7a64gKKS7k+L.undefined [com.liveperson.liveEngage.ssoIdpLogin.LoginVerification]
17:45:41,911 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) java.lang.RuntimeException: Timed out waiting for operation
17:45:41,912 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:134)
17:45:41,912 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.set(CouchbaseClient.java:1188)
17:45:41,912 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.put(CouchbaseReadWriteCache.java:40)
17:45:41,912 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.put(CouchbaseReadWriteCache.java:17)
17:45:41,912 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.LEUsersCacheManager.setSessionDataCache(LEUsersCacheManager.java:121)
17:45:41,912 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.ssoIdpLogin.LoginVerification.writeLoginDataToJbossCache(LoginVerification.java:246)
17:45:41,913 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.ssoIdpLogin.LoginVerification.verifySsoLogin(LoginVerification.java:87)
17:45:41,913 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.AuthFilter.doFilter(AuthFilter.java:71)
17:45:41,913 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveengage.authentication.filters.AuthenticationByProtocolFilter.doFilter(AuthenticationByProtocolFilter.java:71)
17:45:41,913 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
17:45:41,913 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
17:45:41,914 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.CommonFilter.doFilter(CommonFilter.java:35)
17:45:41,914 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
17:45:41,914 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
17:45:41,914 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
17:45:41,914 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
17:45:41,914 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:125)
17:45:41,915 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91)
17:45:41,915 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.JvmRouteValve.invoke(JvmRouteValve.java:88)
17:45:41,915 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.LockingValve.invoke(LockingValve.java:56)
17:45:41,915 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
17:45:41,915 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
17:45:41,916 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
17:45:41,916 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
17:45:41,916 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
17:45:41,916 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:490)
17:45:41,916 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:480)
17:45:41,916 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039)
17:45:41,917 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.lang.Thread.run(Thread.java:722)
17:45:41,917 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) Caused by: net.spy.memcached.internal.CheckedOperationTimeoutException: Timed out waiting for operation - failing node: tlv-le-couchbase-int1.tlv.lpnet.com/192.168.24.184:11210
17:45:41,918 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:159)
17:45:41,918 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:132)
17:45:41,918 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) ... 28 more

OR

19:21:47,997 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) [ERROR] [ajp--127.0.0.1-8020-3] Verify Sso Login failed. sessionId - 6tJElgOsTUcr-7lWgJlWh2HV.undefined [com.liveperson.liveEngage.ssoIdpLogin.LoginVerification]
19:21:47,997 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) java.lang.ArrayIndexOutOfBoundsException: -1
19:21:47,998 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.util.ArrayList.elementData(ArrayList.java:371)
19:21:47,998 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.util.ArrayList.get(ArrayList.java:384)
19:21:47,998 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
19:21:47,998 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.vbucket.VBucketNodeLocator.getServerByIndex(VBucketNodeLocator.java:112)
19:21:47,999 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.observe(CouchbaseClient.java:1621)
19:21:47,999 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.observePoll(CouchbaseClient.java:1750)
19:21:47,999 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.set(CouchbaseClient.java:1199)
19:21:47,999 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.put(CouchbaseReadWriteCache.java:40)
19:21:48,000 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.put(CouchbaseReadWriteCache.java:17)
19:21:48,000 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.LEUsersCacheManager.setSessionDataCache(LEUsersCacheManager.java:121)
19:21:48,000 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.ssoIdpLogin.LoginVerification.writeLoginDataToJbossCache(LoginVerification.java:246)
19:21:48,001 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.ssoIdpLogin.LoginVerification.verifySsoLogin(LoginVerification.java:87)
19:21:48,001 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.AuthFilter.doFilter(AuthFilter.java:71)
19:21:48,001 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveengage.authentication.filters.AuthenticationByProtocolFilter.doFilter(AuthenticationByProtocolFilter.java:71)
19:21:48,002 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
19:21:48,002 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
19:21:48,002 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.CommonFilter.doFilter(CommonFilter.java:35)
19:21:48,002 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
19:21:48,003 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
19:21:48,003 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
19:21:48,003 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
19:21:48,003 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:125)
19:21:48,004 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91)
19:21:48,004 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.JvmRouteValve.invoke(JvmRouteValve.java:88)
19:21:48,004 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.LockingValve.invoke(LockingValve.java:56)
19:21:48,004 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
19:21:48,005 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
19:21:48,005 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
19:21:48,005 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
19:21:48,005 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
19:21:48,006 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:490)
19:21:48,006 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:480)
19:21:48,006 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039)
19:21:48,006 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.lang.Thread.run(Thread.java:722)

Hopefully it's the same one, but just in case, here's another one:
17:41:34,231 ERROR [stderr] (Couchbase View Thread for node tlv-le-couchbase-int2.tlv.lpnet.com/192.168.24.185:8092) 2012-12-10 17:41:34.231 INFO com.couchbase.client.ViewNode: I/O reactor terminated for tlv-le-couchbase-int2.tlv.lpnet.com
17:42:23,120 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) [ERROR] [ajp--127.0.0.1-8020-2] Exception while trying to remove data from cache for session id: y6mpopojZkaJDcWeRDL4J0xp.undefined [org.apache.jsp.views.logout_jsp]
17:42:23,121 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
17:42:23,121 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.util.ArrayList.rangeCheck(ArrayList.java:604)
17:42:23,122 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.util.ArrayList.get(ArrayList.java:382)
17:42:23,122 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
17:42:23,122 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.vbucket.VBucketNodeLocator.getServerByIndex(VBucketNodeLocator.java:112)
17:42:23,123 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.observe(CouchbaseClient.java:1624)
17:42:23,123 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.observePoll(CouchbaseClient.java:1753)
17:42:23,124 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.couchbase.client.CouchbaseClient.delete(CouchbaseClient.java:1113)
17:42:23,124 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.remove(CouchbaseReadWriteCache.java:28)
17:42:23,124 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.CouchbaseReadWriteCache.remove(CouchbaseReadWriteCache.java:17)
17:42:23,125 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.cache.LEUsersCacheManager.removeDataFromCache(LEUsersCacheManager.java:132)
17:42:23,125 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.jsp.views.logout_jsp._jspService(logout_jsp.java:82)
17:42:23,125 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
17:42:23,126 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17:42:23,126 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
17:42:23,126 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
17:42:23,127 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
17:42:23,127 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
17:42:23,127 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
17:42:23,128 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
17:42:23,128 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.ExceptionFilter.doFilter(ExceptionFilter.java:26)
17:42:23,128 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
17:42:23,129 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
17:42:23,129 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveengage.authentication.filters.SSOAuthorizationFilterChain.doFilter(SSOAuthorizationFilterChain.java:30)
17:42:23,130 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.AuthFilter.doFilter(AuthFilter.java:65)
17:42:23,130 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveengage.authentication.filters.AuthenticationByProtocolFilter.doFilter(AuthenticationByProtocolFilter.java:71)
17:42:23,130 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
17:42:23,131 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
17:42:23,131 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at com.liveperson.liveEngage.filters.CommonFilter.doFilter(CommonFilter.java:35)
17:42:23,132 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
17:42:23,132 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
17:42:23,133 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
17:42:23,133 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
17:42:23,133 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:125)
17:42:23,134 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91)
17:42:23,134 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.JvmRouteValve.invoke(JvmRouteValve.java:88)
17:42:23,134 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.session.LockingValve.invoke(LockingValve.java:56)
17:42:23,135 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
17:42:23,136 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
17:42:23,136 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
17:42:23,136 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
17:42:23,137 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
17:42:23,137 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:490)
17:42:23,137 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:480)
17:42:23,138 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039)
17:42:23,140 INFO [stdout] (AsyncAppender-Dispatcher-Thread-56) at java.lang.Thread.run(Thread.java:722)

[JCBC-190] Allow ComplexKeys to work with Floats (not only Doubles)

Fri, 18 Jan 2013 03:57:33 -0600

See: http://www.couchbase.com/forums/thread/set-floating-point-key-couchbase-client-1-1-0-jar

[JCBC-165] ComplexKey does not support partial compound keys with single field

Thu, 6 Dec 2012 03:05:40 -0600

I can't figure out how to do partial compound keys with a single value --

ex. 1 - Specifying both parts of the key:
http://localhost:8092/bucketname/_design/mydesigndoc/_view/myview?group_level=1&startkey=["0",1351742400000]&endkey=["Z",1353073898844]

ex. 2 - Only specifying the first part of the key:
http://localhost:8092/bucketname/_design/mydesigndoc/_view/myview?group_level=1&startkey=["0"]&endkey=["Z"]

I can get ex. 1 to work via the Java client library, but I've had no luck with ex. 2. I've tried setting ranges, complex keys and regular keys. The closest I get is a query string where the "[" and "]" have been escaped which results in a bad URL. I was only able to get this far by manually concatenating the "[" and "]" onto my key and using the query.setKey(String) method.

I believe that ComplexKey should be able to handle ex 2 by calling ComplexKey.of("0") and ComplexKey.of("Z").

[JCBC-155] add javadoc for AbstractView, View, SpatialView

Mon, 3 Dec 2012 05:36:19 -0600

When fixing up a test after a merge commit, I noted that I had to create a View object directly. In the process, I found that many of these classes are public, have public ctors, but have no javadoc. The client API takes AbstractView as an argument, so it may be tempting to just construct one. Is it correct to do so? Maybe. Javadoc doesn't tell me much.

The arguments to the ctors could also be expanded as they're a bit outside code style. Specifically, variable names should be meaningful and at least three or more characters if the variable is to be around for a while.

[JCBC-152] Document testing procedures for unit/functional tests

Dependency — Mon, 3 Dec 2012 05:36:19 -0600

It would be good to have clear documentation in the repo about how to:

(1) run individual tests
(2) change cluster parameters
(3) write more tests

This might be trivial or obvious to do, but very much needed.

For an example of what should be available, see:

(This does not say how to run individual tests though)
https://github.com/couchbase/libcouchbase#run-the-testsuite-towards-a-running-cluster

A more extensive example for a more complex test suite:
https://github.com/couchbase/php-ext-couchbase/blob/master/TESTING.pod

I'm marking this as a 'library' bug because this would require some detailed knowledge of how the tests are written :)

[JCBC-148] Issue with Observe API Persist.TWO and 1 dead node: Time Out when doing set operation

Mon, 3 Dec 2012 03:37:02 -0600

I have a very simple Java program that connect to the 2 nodes and do a set with the following code:

1. So I try to connect to multiple nodes
{code}
            List<URI> couchbaseServerUris = new ArrayList<URI>();
            couchbaseServerUris.add( new URI("http://192.168.0.108:8091/pools") );
            couchbaseServerUris.add( new URI("http://192.168.0.104:8091/pools") );
            CouchbaseClient client = new CouchbaseClient( couchbaseServerUris , "default" , "" );
{code}

2. Then I call the set operation
{code}

        OperationFuture<Boolean> stored = client.set( "my-dummy-key",0, "{\"name\" : \"foo\", \"title\" : \"bar-test\"}", PersistTo.TWO);
{code}

---
So everything is working as expected when the 2 nodes are up.

When I kill 1 node (for example : disconnecting, or stopping, or pausing the Ubuntu VM) I have the following behavior:

When I execute this program:
1- I have an exception saying that 1 node is down : Expected behavior (even if we could avoid a long stack trace)
{code}
2012-11-18 08:14:55.830 WARN com.couchbase.client.vbucket.ConfigurationProviderHTTP: Connection problems with URI http://192.168.0.108:8091/pools ...skipping
java.net.ConnectException: Host is down
{code}

2- When I do the set the program is stopped/blocked until it reaches a network timeout
2012-11-18 08:20:13.462 INFO com.couchbase.client.CouchbaseConnection: Shut down Couchbase client
{code}
Error while storing : Observe Timeout - Polled Unsuccessfully for at least 40 seconds.
2012-11-18 08:20:13.466 INFO done : true
done : {OperationStatus success=false: Observe Timeout - Polled Unsuccessfully for at least 40 seconds.}
com.couchbase.client.ViewNode: Couchbase I/O reactor terminated
2012-11-18 08:20:13.467 INFO com.couchbase.client.ViewNode: Couchbase I/O reactor terminated
{code}

Note that it is only happening with PersistTo.TWO
if I use PersistTo.MASTER or PersistTo.ONE : the program is executed with no error and no stop
if I use PersistTo.THREE ( or more) : the program is executed, no stop with the expected observe message : ( Error while storing : Requested persistence to 3 node(s), but only 2 are available.
)

[JCBC-134] resubscriber IllegalArgumentException during topology changes

Dependency — Wed, 23 Jan 2013 02:06:51 -0600

Exception in thread "couchbase cluster resubscriber - running" java.lang.IllegalArgumentException: Bucket name cannot be null and must never be re-set to a new object.
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.subscribe(ConfigurationProviderHTTP.java:240)
        at com.couchbase.client.vbucket.ConfigurationProviderHTTP.finishResubscribe(ConfigurationProviderHTTP.java:215)
        at com.couchbase.client.CouchbaseConnectionFactory$Resubscriber.run(CouchbaseConnectionFactory.java:322)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)

Unfortunately I don't have a whole lot more insight into what's happening, but the stack trace might be helpful to examine.. assigning to myself until I have more info..

[JCBC-125] Don't cast view documents to strings

Mon, 3 Dec 2012 05:36:20 -0600

When objects are stored as non-strings in Couchbase and then loaded through a View, the SDK currently casts every document to a string. This works fine for JSON documents, but as soon as you want to store serialized objects it breaks.

Implicit casting is not needed in this place (see fix).

[JCBC-97] documentation needs a discussion on JSON mapping, getting started needs an example of using JSON

Wed, 22 Aug 2012 10:20:48 -0500

At one point, I thought we had a discussion of JSON document usage in the getting started and on the web page. It's not there now, but we need to have a discussion about how a Java developer maps their high-level objects into JSON.

[JCBC-74] Implement observe command

Wed, 22 Aug 2012 10:19:12 -0500

Add the basic low level observe command

[JCBC-72] View query returns null

Wed, 11 Jul 2012 17:38:21 -0500

viewResponse return null, and i can't figure out why:

• I execute my code
CouchbaseClient c = new CouchbaseClient(baseURIs, "default", "");
View view = c.getView("dev_lenders", "country_count");

Query query = new Query();
Stale stale=Stale.OK;
query.setStale(stale);
query.setGroup(true);
ViewResponse viewResponse = c.query(view, query);

• My viewRespons is null.

• Checking the couchdb.1 log, I see:
[couchdb:info] [2012-07-04 21:40:50] [ns_1@127.0.0.1:<0.24865.33>:couch_log:info:39] 10.32.5.29 - - GET /default/_design/dev_lenders/_view/country_count?group=true&stale=ok 200

• Running this URL directly against my server I do get results:
http://10.2.1.12:8092/default/_design/dev_lenders/_view/country_count?group=true&stale=ok
{"rows":[
{"key":null,"value":4171},
{"key":"AE","value":5},
{"key":"AF","value":1},
{"key":"AM","value":2},
...

Not sure what logs i can provide to debug this further. let me know how i can help.

[JCBC-59] authentication not working correctly with CouchbaseConnectionFactoryBuilder

Mon, 6 Aug 2012 18:47:15 -0500

The use of the CouchbaseConnectionFactoryBuilder like so yields a client that does not authenticate correctly.

CouchbaseConnectionFactoryBuilder cfb = new CouchbaseConnectionFactoryBuilder();
CouchbaseConnectionFactory cf = cfb.buildCouchbaseConnection(servers, "default_jOWPgw", "default_jOWPgw", "testing");
CouchbaseClient client = new CouchbaseClient(cf);

[JCBC-22] Spring Support for CouchbaseClient

Thu, 31 Jan 2013 09:15:13 -0600

We need to add support for the following Spring Integration Parts:

- General Info on how to use the Client with Spring Beans
- Caching Support through @Cacheable annotations
- Spring Data Support (yet to be defined).

Current progress of the (yet unofficial support) can be tracked here: https://github.com/couchbaselabs/couchbase-spring

[JCBC-254] handle NOT_FOUND responses in observe() method for delete observe situations

Wed, 27 Feb 2013 15:08:53 -0600

handle NOT_FOUND responses in observe() method for delete observe situations

[JCBC-253] Observe timing out when failing over

Wed, 27 Feb 2013 13:51:01 -0600

When using observe commands and a node is failed over and not rebalanced automatically, the code will time out because no broadcast will ever return but it expects one.

Proposed solution is to throw an exception to fail fast when there is no replica available.

[JCBC-243] Docs: Reference installation

Duplicate — Mon, 11 Feb 2013 06:22:50 -0600

Customers have lots of choices at their fingertips, and many of those choices will result in a non-functioning installation, or at least a lot of time spent figuring out what the right pieces are.

Can we please provide as much details as possible about a reference installation that we can be sure will work for a customer who is just getting started? This is outside of our support for any one operatin system, but more about telling the customer "if you install with these versions and packages, this code will work"

-OS
-"language" version (JDK 6, etc)
-other packages/modules required and/or tested with

[JCBC-236] Error handling documentation

Duplicate — Wed, 6 Feb 2013 03:23:50 -0600

Please create some documentation specifying possible error/failures to operations, what they "look" like in the logs/exceptions/stack traces and what our recommendation is on how to handle them.

i.e. tmp_oom, timeouts (connection/operation/java-internal/etc), "get miss" (it's technically a failure, let's make it overly obvious what it means), CAS failure, add() failure, replace() failure,

Some of this should be covered in the API reference, but this bug is specifically for a single page where this information is aggregated that a customer/user could read about how to handle errors.

[JCBC-232] Javadoc jar files should be renamed to be compliant with IDEs

Tue, 26 Mar 2013 01:31:47 -0500

IntelliJ Idea won't automatically download couchbase-client-*-javadocs.jar or spymemcached-*-javadocs.jar from http://files.couchbase.com/maven2/ because they have an "s" at the end of "javadoc".
I don't know whether any other IDE's have trouble with this, but the standard appears to be "XXX-javadoc.jar" instead of "XXX-javadocs.jar".
The executable and source jars download fine.
Can this be changed for a future version?

See : http://www.couchbase.com/forums/thread/java-sdk-javadoc-maven-download-problem

[JCBC-226] Delete's get() doesnt return the right value

Wed, 27 Feb 2013 15:25:55 -0600

Deleting is faulty, I asked for get() which should wait for the result, but every 5th returns with false, however the deletion has performed.

I have attached a sample code and the output result.

[JCBC-224] Functional Integration tests failure tracking.

Dependency — Wed, 30 Jan 2013 00:39:29 -0600

I am raising this JCBC issue as a blocker for the SDKQE task.

The new observations that are coming everyday on the test runs would be updated here and if those are identified as major issues which could be fixed in the release 1.1.2, should be fixed as part of this task.

I understand that we dont have a build ready now. But it would be good to track the issues and fix them as a preventive measure for the upcoming build.

[JCBC-223] Cannot use Persist.ONE/MASTER on a single node installation

Duplicate — Thu, 31 Jan 2013 10:00:13 -0600

Using the default bucket I am trying to use the simple "Durability" option using the following code:

----
            {
                System.out.println("Set a Key-Value and Get the Key-Value");
                OperationFuture op = cb.set("mytest", 0, "my value", PersistTo.MASTER);
                System.out.println("cb.get(\"mytest\")" + " => " + cb.get("mytest") + "\"");
                System.out.println("");
            }
----

This raises the following exception:
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(ArrayList.java:324)
at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
at com.couchbase.client.vbucket.VBucketNodeLocator.getServerByIndex(VBucketNodeLocator.java:112)
at com.couchbase.client.CouchbaseClient.observe(CouchbaseClient.java:1601)
at com.couchbase.client.CouchbaseClient.observePoll(CouchbaseClient.java:1730)
at com.couchbase.client.CouchbaseClient.set(CouchbaseClient.java:1179)
at com.couchbase.client.CouchbaseClient.set(CouchbaseClient.java:1211)
at com.couchbase.devday.Ex02Storage.main(Ex02Storage.java:36)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)

I am using the code available at :
https://github.com/couchbaselabs/DeveloperDay
https://github.com/couchbaselabs/DeveloperDay/blob/master/Java/basic-operations/src/main/java/com/couchbase/devday/Ex08Observe.java
(this example does not contain the PersistTo.ONE or MASTER since it does not work on a single node.
but as you can see this is a very basic sample code

[JCBC-220] Spymemcached doesn't flush the queues correctly during bulk loads

Mon, 28 Jan 2013 05:51:52 -0600

CB:2.0
Library: 1.1.1
There is data loss in couchbase 2.0 when using the set command and the couchbase bucket . Loss seem to be severe the longer away the servers are from the client. Same java client works well with memcached buckets in 2.0, and both couchbase and memcached buckets in 1.8.1. See screenshots below. Note the item count in the couchbase bucket which is missing 24% of the data.
Attached Image for the total items stored in the couchbase bucket. Only 750K items stored for 1M inserts.

On bulk loads using the 1.1.1 library, the customer is seeing data loss for the items that have been set.

The customer tried to set 1M items using the latest Java Client 1.1.1 and figured out that all the items are getting persisted.

An update from the customer.......

I have rewritten it a bit and reproduced the problem here. Find the updated version enclosed where you can see the issue being reproduced. You will see that the number of keys reported by couchbase is not the number of keys that we have inserted.

It seems that the problem is in the handling of queueing the set calls internally in the driver. I.e, if we don't actively force the "async" queues to flush (by calling the future get()), data on the queues could be discarded. So this sounds like a spymemcached bug where it does not correctly flush the queues during high loads? According to the javadoc we should have seen the below, and if not, we should have assumed that all operations were properly processed?

java.lang.IllegalStateException - in the rare circumstance where queue is too full to accept any more requests

Attache code using which we were able to reproduce this error on bulk loads.

[JCBC-218] CLONE - Client constructor blocks or deadlocks

Wed, 27 Feb 2013 15:28:50 -0600

I am evaluating the couchbase product and hit a brick wall immediately when running through the simple hello world example.

I have a 3 node cluster running couchbase enterprise 1.8.2 on ubuntu 10.04 64 bit VMware images. All three are running in VMWare player instances on Windows 7 64bit.

When I try to run the Main example on Windows 7 using Java6 (64 bit) the code blocks somewhere in the Client constructor. The result is the logging below.

2012-06-14 14:07:46.313 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.150:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 14:07:46.316 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.151:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 14:07:46.319 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.152:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 14:07:59.843 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@24a4e2e3
2012-06-14 14:08:52.983 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@21ec6696
2012-06-14 14:08:52.987 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@27431340

I have also tried debugging but the code blocks in the constructor at

client = new CouchbaseClient(uris, "default", "");

The program never completes.

This works fine in a Linux environment with the following output received

2012-06-14 04:58:50.693 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.150:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 04:58:50.703 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.151:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 04:58:50.708 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/192.168.186.152:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-14 04:58:50.830 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@1bc74f37
2012-06-14 04:58:50.834 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@3a21b220
2012-06-14 04:58:50.843 INFO com.couchbase.client.CouchbaseConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@732b3d53
2012-06-14 04:58:51.135 INFO com.couchbase.client.CouchbaseConnection: Shut down Couchbase client
Set Succeeded
Synchronous Get failed
Asynchronous Get Succeeded: Hello World!

Is there a JDK for windows 7 or a configuration setting that can be used to prevent this?

[JCBC-216] buildinfo class is not packaged properly

Fri, 18 Jan 2013 03:56:29 -0600

The buildinfo class should be getting packaged properly.

$ java -jar build/jars/couchbase-client-1.1.0.jar
Exception in thread "main" java.lang.NoClassDefFoundError: com/couchbase/client/BuildInfo
Caused by: java.lang.ClassNotFoundException: com.couchbase.client.BuildInfo
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
$ jar -tvf build/jars/couchbase-client-1.1.0.jar | grep BuildInfo

[JCBC-215] Refactor viewmode property loading

Fri, 18 Jan 2013 00:54:14 -0600

After having the CouchbaseProperties class in place as a centralized repository for both system and file-based properties, the "viewmode" should also use this code.

[JCBC-214] client does not failover properly when bootstrap node fails in a soft way

Fri, 18 Jan 2013 00:16:48 -0600

If a given server just stops responding to TCP on both 8091 and 11210 (which can be simulated with a pkill -STOP), the client does not detect this failure mode and never recovers.

[JCBC-212] Add new throttling feature to allow us to keep from using all system memory

Fri, 18 Jan 2013 00:16:30 -0600

When doing things like bulk loading, there are times we have multiple workload profiles. Interactive applications using the same client and same server need "room to move" and should always be fast, while other workloads should throttle themselves.

The intent here would be to add a feature such that:
for every N operations, pull stats from the nodes
if the amount of memory used is below high_wat, don't do anything
else if the amount of memory used is 10% of the remaining memory above high_wat before max memory usage, insert a sleep of Y milliseconds before each operation, and log the backoff at a debug level, check stats again ever M operations
else if the amount of memory used is greater than 10% above that level above high_wat, insert a sleep of Z milliseconds before each operation and log the backoff at an info level, check stats again every O operations
Turning this on or off should be done via a properties file or just simple -D args to the JVM, either one is okay.

N, M, O and Y, Z should all be tuneable, either via a properties file or a define. All of them should be optional.

Default values should be:
N = 10000
M = N/100
O = M/10

Y = 1ms
Z = Y * 3

[JCBC-211] Refactor property management into a centralized class.

Thu, 31 Jan 2013 10:07:23 -0600

Refactor property management into a centralized class.

[JCBC-210] Throw CancellationException instead of RuntimeException on op cancel

Thu, 21 Feb 2013 07:35:46 -0600

This is only a semantical change because CancellationExceptions are children of RuntimeExceptions, but it should give us better debugabillity in production deployments and those Exceptions can be better caught.

[JCBC-191] DOC: missing reference to "maven repository" in the tutorial

Wed, 19 Dec 2012 11:31:44 -0600

The following page of the tutorial : ( 2.1.1. Project Setup )

http://www.couchbase.com/docs/couchbase-sdk-java-1.1/preps-project.html

show some information of the POM file, we need to be sure we also include the repository in all the docs:

we need to add this:
<repositories>
  <repository>
    <id>couchbase</id>
    <name>Couchbase Maven Repository</name>
    <layout>default</layout>
    <url>http://files.couchbase.com/maven2/</url>
    <snapshots>
      <enabled>false</enabled>
    </snapshots>
  </repository>
</repositories>

This is what it done here:
http://www.couchbase.com/docs/couchbase-sdk-java-1.1/downloading.html

[JCBC-192] DOC : Downloading page mention the 1.1 BETA

Wed, 19 Dec 2012 11:35:09 -0600

The page: Downloading fo the Java SDK
http://www.couchbase.com/docs/couchbase-sdk-java-1.1/downloading.html

mentions
couchbase-client-1.1-beta.jar

it should be
couchbase-client-1.1.0.jar

[JCBC-188] Tutorial quickstart

Wed, 6 Feb 2013 03:26:44 -0600

I think it worth to add quickstart section in the java tutorial to help people first quickly start the application and then experimenting while reading the rest of the tutorial. I've wrote and Michael merged already README file describing how to do it. Would be nice if some parts of it will be published in the tutorial: https://github.com/couchbaselabs/beersample-java/blob/master/README.markdown

I left an output of the terminal commands, because they will show what people should expect

[JCBC-186] there is no CouchbaseCacheManager in 1.1.0, but in the API reference

Mon, 17 Dec 2012 10:56:26 -0600

There is no CouchbaseCacheManager in the 1.1.0 SDK, but it seems to be in the API reference. Something like this is being worked on soon.

See http://www.couchbase.com/forums/thread/which-jar-couchbasecachemanager

[JCBC-185] autodocs don't have links to spymemcached methods (i.e., most of the API)

Mon, 7 Jan 2013 11:23:47 -0600

It's great to have the generated docs for the Java client available on the website. However, it is confusing for a lot of people because most of the API methods aren't documented there, they are inherited from spymemcached and the docs don't link to spymemcached classes.

If it is technically possible, it would be great to have live links in the autodocs for all the methods, including spymemcached ones.

If not, it would be good to have a disambiguation page or some kind of explanation that, to get a complete view of the api docs, one must read both the spymemcached and couchbase docs. And a link to http://www.couchbase.com/autodocs/java/spymemcached/2.8.3/index.html (or whatever the latest link is).

[JCBC-178] Java Client's Manual 1.1

Wed, 6 Feb 2013 03:26:54 -0600

Following are the review comments :

1) Chapter 11. Line - 'The other alternative is create a logging.properties and add it to your in your classpath:'
2) Chapter 8. --> Table 8.1 --> line 2 --> Append a value to an existing key with custom transcoder.
Also, incr and decr operation descriptions are the same for the three overloaded methods.
3) There is no mention of ViewConnection class and the methods like createViewConnection in the chapter 10 on Views and Queries.
4) The version of couchbase-client jar that is shown in the snap shots in the document is 1.1-dp2 and not 1.1-dp4.
5) Also, there is no mention of the helper classes for eg. BucketTool and their functionalities.
6) Chapter 6 --> section 6.2 should mention about Add with Observe like section 6.3 is about set with observe.
7) Couchbase client also has the methods observe and observePoll which have not been described in the manual.
8) Appendix A3 - mentions about the addition of delete and observe functionality on the server build 1553 and above, but the manual doesn't have a section on delete with observe in section 8.4.
9) Chapter 7. Table 7.1 - client.getAndLock(key [, getl-expiry ], transcoder) method is not hyperlinked.
10) Chapter 7. - only one 'unlock' method is defined, however in the API, there are two overloaded methods.
11) The getDesignDocument method is not defined in any chapter inside the manual.
12) Spatial Views and map reduce views are not defined in Chapter 10.
Also the API methods to fetch the spatial views/paginator query have not been elaborated.
13) Chapter 9. - getKeyStats method is not defined.
14) Chapter 5, table 5.1 - string 'client.new' should be replaced with 'new'.
15) Chapter 4, Table 4.1 - Three add operations are not hyper-linked.
16) Section 4.3, Line - 'You can also use a custom transcoder the serialization of objects. This can be to serialize objects in a format that is com-
patible with other languages or environments.' needs revision.
17) Instead of Query.new(), it should be new Query().
18) Chapter 5 - Connection Operations need to be elaborated in more detail. Other that CouchbaseClient, there are other classes which act as the helper classes for building the client to server connection.

[JCBC-176] Using BucketTool helper - error in connection to the server, bucket creation, deletion.

Dependency — Thu, 31 Jan 2013 09:28:14 -0600

BucketTool is not behaving properly to create default bucket and connect to the server.
Error received while running CouchbaseClientTest using the initClient method which is overridden -

java.lang.RuntimeException: Http Error: 401 Reason: Unauthorized Details: No reason given
at com.couchbase.client.ClusterManager.checkError(ClusterManager.java:300)
at com.couchbase.client.ClusterManager.listBuckets(ClusterManager.java:186)
at com.couchbase.client.BucketTool$1.callback(BucketTool.java:73)
at com.couchbase.client.BucketTool.poll(BucketTool.java:108)
at com.couchbase.client.BucketTool.deleteAllBuckets(BucketTool.java:84)
at com.couchbase.client.CouchbaseClientTest.initClient(CouchbaseClientTest.java:60)
at net.spy.memcached.ClientBaseCase.setUp(ClientBaseCase.java:72)
at junit.framework.TestCase.runBare(TestCase.java:132)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

[JCBC-175] Small typo in Exception message "Node exepcted to receive data is inactive"

Tue, 11 Dec 2012 04:05:36 -0600

Small typo in Exception message "Node exepcted to receive data is inactive"

[JCBC-167] ComplexKey converts longs to strings

Mon, 17 Dec 2012 01:32:22 -0600

I previously added this as a comment on ~~JCBC-41~~

        Query q1 = new Query();
        long time1 = 0;
        long time2 = 99999999;
        long time3 = 99999999999l;

        q1.setRangeStart(ComplexKey.of(time1));
        q1.setRangeEnd(ComplexKey.of(time2));
        q1.toString() --> ?startkey=0&endkey=99999999

        q1.setRangeStart(ComplexKey.of(time1));
        q1.setRangeEnd(ComplexKey.of(time3));
        q1.toString()) --> ?startkey=0&endkey=%2299999999999%22

It's throwing quotes around the long value.

[JCBC-159] 1.0.4 in release notes but not available for d/l

Thu, 31 Jan 2013 23:39:11 -0600

Not sure if this is really a docs bug, but we need to address the inconsistency between what is avialable for d/l and the latest release notes.

[JCBC-157] Unsure if CouchbaseConnectionFactory.pastReconnThreshold really does what it's suppose to do

Mon, 3 Dec 2012 03:26:46 -0600

{code}
  private boolean pastReconnThreshold() {
    long currentTime = System.nanoTime();
    if (currentTime - thresholdLastCheck > 100000000) { //if longer than 10 sec
      configThresholdCount = 0; // it's been more than 10 sec since last
                                // tried, so don't try again just yet.
    }
    configThresholdCount++;
    thresholdLastCheck = currentTime;

    if (configThresholdCount >= maxConfigCheck) {
      return true;
    }
    return false;
  }
{code}

Does the above really work as expected? It looks strange. 100000000 in nanos is only 100 millis and not 10 seconds as stated in comments.
If there is more than 100 millis between calls we always reset configThresholdCount and will never return true, which seems very strange.

[JCBC-156] several javadoc warnings emitted

Mon, 3 Dec 2012 05:36:19 -0600

During build of javadoc:

  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:128: warning - @param argument "memorySize" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:143: warning - @param argument "memorySize" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:143: warning - @param argument "password" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ClusterManager.java:158: warning - @param argument "memorySize" is not a parameter name.
  [javadoc] /Users/ingenthr/src/couchbase-java-client/src/main/java/com/couchbase/client/ViewConnection.java:199: warning - @return tag has no arguments.

[JCBC-145] Add the maven XML snippet to the getting started guide (both web page and docs)

Tue, 13 Nov 2012 09:34:17 -0600

Our current maven documentation is limited to telling people what the repo URL is. This often isn't enough, and they need the groupId and artifactId. Best would be to describe it similar to:
http://code.google.com/p/spymemcached/wiki/Maven

[JCBC-143] Prepend should not require CAS

Duplicate — Fri, 21 Dec 2012 02:28:52 -0600

Hopefully this is just a doc bug and not in the actual code, but all of the atomic updates including prepend (http://www.couchbase.com/docs/couchbase-sdk-java-1.0/couchbase-sdk-java-update-prepend.html) should not require CAS. That significantly defeats their performance effectiveness.

If the function *does* require CAS, we should document that a CAS id of 0 will override the requirement to get the key again as in this example:
client.prepend(casv.getCas(),"samplekey", "prependedstring");

[JCBC-139] 'delete & persist' and' delete, persist and replicate' functionalities not supported in 1.1-dp3 SDK.

Wed, 14 Nov 2012 05:58:55 -0600

couchbase-sdk-java-1.0 Manual has presented the usage specific to the 'delete & persist' and' delete, persist and replicate' functionalities but the SDK API's dont support this functionality due to an ongoing defect in the the couchbase server. Similar issue is there with the 'set and persist' and 'set and replicate' functionalities.
The manual needs to be updated accordingly.

[JCBC-141] Graceful Shutdown Test fails on dp4

Mon, 3 Dec 2012 05:36:20 -0600

The gracefulShutdown test on the CouchbaseClient fails.

More inspection needed before we hit a stable release!

[JCBC-137] During the failure Java client cannot do any operations

Sun, 4 Nov 2012 20:11:43 -0600

We simulated the split-brain by blocking all network traffic on one node for a minute. We used iptables with DROP target.
During the failure the client cannot do any operations.
During this minute the console doesn't even say that any node is down.

Is this a correct behavior? Can client work with a part of the cluster?

I see the client has some possible failure modes: http://www.couchbase.com/autodocs/java/spymemcached/2.8.3/index.html?net/spy/memcached/FailureMode.html

Which is the best to allow client to be functional while one node of the cluster is down?
I cannot chose from this API docs short description :(

Tried all three options for FailureMode.
Always the same behavior: client cannot do any requests.

[JCBC-136] Add support for spatial view queries

Dependency — Mon, 3 Dec 2012 05:36:20 -0600

Add support for spatial view queries

[JCBC-124] Cannot operate on keys with spaces in them

Tue, 9 Oct 2012 15:14:56 -0500

The other clients allows keys with spaces in them, such as "test key", but there is no way to operate on these using the Java client.

myclient.set("test key", 0, "test value");

java.lang.IllegalArgumentException: Key contains invalid characters: ``test key''
at net.spy.memcached.util.StringUtils.validateKey(StringUtils.java:79)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:300)
at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:733)

[JCBC-135] Using Couchbase inside netty server fails

Tue, 26 Mar 2013 00:51:55 -0500

See this forum question for a description of the issue as well as the fix for it:

http://www.couchbase.com/forums/thread/using-couchbaseclient-inside-netty-server

[JCBC-131] Java Sample Application

Tue, 11 Dec 2012 04:54:10 -0600

Create and document the sample application (port the ruby example app to java).

[JCBC-127] Publish Couchbase Java SDK Javadoc online, and as a complete resource (zip)

Wed, 7 Nov 2012 10:42:28 -0600

Publish Couchbase Java SDK Javadoc online, and as a complete resource (zip)

[JCBC-123] ArrayOutOfBounds exception during failover

Duplicate — Mon, 3 Dec 2012 05:36:20 -0600

While running a sequence of getsAsync operations, the entry point/bootstrap node is failed over. The output follows

Exception in thread "SDK Handle-8" java.lang.ArrayIndexOutOfBoundsException: -1
        at java.util.ArrayList.elementData(ArrayList.java:338)
        at java.util.ArrayList.get(ArrayList.java:351)
        at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
        at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:74)
        at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:144)
        at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
        at net.spy.memcached.MemcachedClient.asyncGets(MemcachedClient.java:888)
        at net.spy.memcached.MemcachedClient.asyncGets(MemcachedClient.java:902)
        at com.couchbase.sdkd.cbclient.GetCommandContext.doOneCommand(GetCommandContext.java:60)
        at com.couchbase.sdkd.cbclient.CommandContext.execute(CommandContext.java:266)
        at com.couchbase.sdkd.server.SdkServer.executeCommand(SdkServer.java:114)
        at com.couchbase.sdkd.server.SdkServer.handleRequest(SdkServer.java:133)
        at com.couchbase.sdkd.server.SdkServer.run(SdkServer.java:187)

[JCBC-118] Improve the docs for observe around the ReplicateTo flag

Wed, 26 Sep 2012 10:04:29 -0500

See the comment to my response of this question.

http://stackoverflow.com/questions/12521102/in-couchbases-observe-feature-what-is-the-difference-between-persistto-and/12521346#comment16856063_12521346

[JCBC-109] Reduce observe poll interval latency

Wed, 12 Sep 2012 17:48:28 -0500

Current observe poll latencies are very long, some 400ms by default. Testing shows latencies can be as low as 10ms in some cases, so to optimize for the best case, we should lower the polling interval to 100ms, but still poll for up to 4000 sec.

JCBC-108 tracks converting this to an adaptive algorithm based on server statistics.

[JCBC-107] OperationStatus message is incorrect if observe poll interval or limit is tuned

Wed, 12 Sep 2012 22:02:54 -0500

OperationStatus message is incorrect if observe poll interval or limit is tuned

[JCBC-106] Upgrade Netty dependency

Tue, 18 Sep 2012 02:23:52 -0500

There have been reports of Couchbase client causing issues with Play Framework due to using an outdated Netty dependency
https://groups.google.com/d/topic/play-framework/_ZnyqUxiem4/discussion

Netty 3.5.5 is currently available from netty,io

[JCBC-105] Expose "stats key" results through client API

Sun, 30 Sep 2012 13:49:21 -0500

Customer request to access per-key metadata information from API:
verification for key foo
key_cas: 1
key_data_age: 0
key_dirtied: 0
key_exptime: 0
key_flags: 0
key_is_dirty: 0
key_last_modification_time: 1346067947
key_valid: valid

[JCBC-104] Cannot discern difference between modified and timed out on synchronous operations - OperationStatus on observed operations does not record the status of the observe

Wed, 12 Sep 2012 22:01:19 -0500

From the synchronous set method, the underlying observePoll() is called but the results of the OperationFuture are set with the result of the status of the mutation, not the result of the status of the observe.

  public OperationFuture<Boolean> set(String key, int exp,
          String value, PersistTo req, ReplicateTo rep) {
    OperationFuture<Boolean> setOp = set(key, exp, value);
    try {
      if (setOp.get()) {
        observePoll(key, setOp.getCas(), req, rep);
      }
    } catch (InterruptedException e) {
      setOp.set(false, setOp.getStatus());
    } catch (ExecutionException e) {
      setOp.set(false, setOp.getStatus());
    } catch (TimeoutException e) {
      setOp.set(false, setOp.getStatus());
    } catch (IllegalArgumentException e) {
      setOp.set(false, setOp.getStatus());
    } catch (RuntimeException e) {
      setOp.set(false, setOp.getStatus());
    }
    return (setOp);
  }

Note that the setOp response is used when setting it's own status, not the status of the observe, which is buried in the exception. The exception is out of scope by the time the response goes back to the caller's code.

[JCBC-102] Client.get() returns null values when using CouchbaseConnectionFactoryBuilder

Thu, 13 Sep 2012 22:47:31 -0500

Java client 1.1-dp seems to have a problem using CouchbaseConnectionFactoryBuilder. Client.get() returns null values regardless of whether a key exists or not. Java client 1.0.3 doesn't have the problem.

With 1.1-dp, if I set up a client like so:

   URI base = new URI(String.format("http://%s:8091/pools", server));
   List<URI> baseURIs = new ArrayList<URI>();
   baseURIs.add(base);
   CouchbaseConnectionFactoryBuilder cfb = new CouchbaseConnectionFactoryBuilder();
   cfb.setOpTimeout(10000);
   cfb.setOpQueueMaxBlockTime(10000);
   CouchbaseConnectionFactory cf = cfb.buildCouchbaseConnection(baseURIs, bucket, "", "");
   CouchbaseClient client = new CouchbaseClient(cf);

then try to get a key like so:

            getFuture = client.asyncGet(key);
            value = (String) getFuture.get(); // value is null

the .get() doesn't fail but the returned value is null.

However, if I set up the 1.1-dp client like so, using just CouchbaseConnectionFactory:

        URI base = new URI(String.format("http://%s:8091/pools", server));
        List<URI> baseURIs = new ArrayList<URI>();
        baseURIs.add(base);
        CouchbaseConnectionFactory cf = new CouchbaseConnectionFactory(baseURIs, bucket, "");
        CouchbaseClient client = new CouchbaseClient(cf);
        getFuture = client.asyncGet(key);
        value = (String) getFuture.get(); // value is not null and contains the document for the key

I want to use CouchbaseConnectionFactoryBuilder because I'm doing a bulk import of millions of documents and I need the timeout/blocking behaviour to prevent swamping the client.

Java client 1.0.3 works correctly - using CouchbaseConnectionFactoryBuilder to build connection factories and clients results in the correct behaviour.

[JCBC-99] Java 1.1 DP exception on failed auth

Tue, 13 Nov 2012 09:07:45 -0600

Stack trace attached. Looks like a few different failures around multi-gets, there are some incomplete binary ops and failed authentications (alongside successful authentications, so I presume the user/pass is actually correct).

[JCBC-96] client IO thread is blocked by the fix applied for JCBC-20, doWrites() needs to put data somewhere for another thread to do the work

Mon, 1 Oct 2012 17:02:29 -0500

In ~~JCBC-20~~, the poll() was changed to a blocking take(), but the problem there is that it's on the IO thread which shouldn't be blocked.

The ViewNode has it's own thread, so this should be moved to that node's thread.

[JCBC-95] view requests do not have HTTP authorization header

Tue, 18 Sep 2012 02:22:18 -0500

Authorization checking has only been recently added to the server and it's been found that view requests are missing authorization headers. This means view requests come back empty, owing to a 401 on request.

[JCBC-94] Shutdown function does not shutdown ViewConnection Thread

Mon, 3 Dec 2012 05:36:20 -0600

The patch (ViewConnection.java) in the bug http://www.couchbase.com/issues/browse/JCBC-26 fixed the dead loop issue, but it introduced another Shutdown issue.
when calling the shutdown function of CouchbaseClient, it could not shutdown the thread of the ViewConnection.

Public void run() {
While(running) {
If (!reconfiguring) {
Synchronized(threadLock)
{
Boolean hasOps = false;
While(!hasOps) { ==> While(!hasOps && running)
For (viewNode node: couchNodes) {
If (node.hasWriteOps()) {
hasOps = true;
break;
}
}
......
If (!hasOps)
{
threadLock.wait();
}
}
}
If (running) {
handleIO();
}

[JCBC-93] Download link is "protected" based on referrer URL

Tue, 7 Aug 2012 19:30:12 -0500

I don't think this makes sense. I believe we can get reasonable download counts from the web server logs. This makes it more difficult for people to access the SDK and may turn people away.

[couch@localhost dist]$ wget --referer=http://www.couchbase.com/develop/java/next http:
//packages.couchbase.com/clients/java/1.1-dp/Couchbase-Java-Client-1.1-dp.zip
--2012-08-01 16:08:49-- http://packages.couchbase.com/clients/java/1.1-dp/Couchbase-Java-Client-1.1-dp.zip
Resolving packages.couchbase.com... 72.21.214.199
Connecting to packages.couchbase.com|72.21.214.199|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1789840 (1.7M) [application/zip]
Saving to: `Couchbase-Java-Client-1.1-dp.zip'

100%[=============================================>] 1,789,840 666K/s in 2.6s

2012-08-01 16:08:53 (666 KB/s) - `Couchbase-Java-Client-1.1-dp.zip' saved [1789840/1789840]

[couch@localhost dist]$ wget http://packages.couchbase.com/clients/java/1.1-dp/Couchbas
e-Java-Client-1.1-dp.zip
--2012-08-01 16:09:03-- http://packages.couchbase.com/clients/java/1.1-dp/Couchbase-Java-Client-1.1-dp.zip
Resolving packages.couchbase.com... 72.21.214.199
Connecting to packages.couchbase.com|72.21.214.199|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2012-08-01 16:09:04 ERROR 403: Forbidden.

[couch@localhost dist]$

[JCBC-92] Java error when a node is removed - need to check for pending state on a bucket

Mon, 3 Dec 2012 05:36:19 -0600

This is related to CBSE-187.

While the test was running we removed a node from the cluster, there were failures due to operation cancelled and TimeoutException and the test didn't continue.
Then we started the test again without adding back the removed node, it just threw:
java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.get(Unknown Source)
at com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:74)
at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:143)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:639)
at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:296)
at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:727)
<supressed>

[JCBC-91] NPE when using malformed URI

Thu, 13 Sep 2012 22:54:13 -0500

Caused by: java.lang.NullPointerException
at com.couchbase.client.CouchbaseConnectionFactory.getVBucketConfig(CouchbaseConnectionFactory.java:154)
at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:156)
at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:125)
at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:77)
at com.playtika.pool.membase.MembasePool.start(MembasePool.java:55)
... 48 more

Would prefer a more meaningful error or exception to indicate that the URI was incorrect

[JCBC-88] if timeout is lowered, client can fail to resubscribe for cluster reconfiguration updates in a failure scenario

Mon, 30 Jul 2012 16:11:31 -0500

The resubscription logic depends on performing the resubscribe from a thread from the application calling us. The problem is that it can take upward of 700ms for this to occur meaning the timeout may yank us away before finishing the resubscribe.

[JCBC-87] incr/decr should return a BigInteger

Mon, 13 Aug 2012 13:11:37 -0500

We can easily incr past the size of a long so we should use something that can hold a value of any size.

[JCBC-86] Remove getHashAlgorithm and verify correct behavior of client

Mon, 3 Dec 2012 05:36:20 -0600

Current CacheConfig class has a getHashAlgorithm method and it seems to define native hash. Since there don't seem to be any uses of this, it should be removed or somehow refactored out.

[JCBC-85] We need a better way to run our view tests

Thu, 31 Jan 2013 09:16:52 -0600

Right now we create a view and the wait for 30 seconds. We should add dome logic to be able to tell exactly when the view is created so that the unit tests run faster.

[JCBC-84] We need more unit tests for views

Thu, 8 Nov 2012 04:16:10 -0600

We need more unit tests for views

[JCBC-81] Update the getting started to match the Beer sample DB

Wed, 5 Dec 2012 11:19:08 -0600

Once the sample DB has been integrated into the server, update the getting started (both on the web page and in the documentation) to use the sample database.

[JCBC-80] Add a unit/integration test validation of OBSERVE + view stale=false

Mon, 3 Dec 2012 05:36:19 -0600

Ensure that when a synchronous set is used with the new low-level observe, the index is fully updated when querying with stale=false.

[JCBC-77] Design document management, including error handling

Fri, 14 Sep 2012 19:33:57 -0500

Add the additional functionality needed to create and replace design documents. This will likely be an extension on the Bucket class.

[JCBC-79] View error options at query time

Thu, 13 Sep 2012 22:42:15 -0500

At view query time, we need to ensure the developer has the ability to add an "on_error" parameter with values of either "stop" or "continue".

[JCBC-78] Bucket management

Fri, 14 Sep 2012 19:19:36 -0500

Add the necessary features to create and remove buckets. Also, add the ability to call the RESTful bucket flush.

[JCBC-75] Highlevel synchronous mutation operations atop observe

Wed, 22 Aug 2012 10:27:57 -0500

Highlevel synchronous mutation operations atop observe

[JCBC-71] Not able to run the sample program

Thu, 23 Aug 2012 11:57:53 -0500

I installed Couchbase Server on my machine with default setting and then tried to run the sample program and got the following error:

2012-06-28 21:12:12.677 INFO com.couchbase.client.CouchbaseConnection: Added {QA sa=/169.254.20.219:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2012-06-28 21:12:17.309 WARN com.couchbase.client.CouchbaseConnection: Node exepcted to receive data is inactive. This could be due to afailure within the cluster. Will check for updated configuration. Key without a configured node is: spoon.
Jun 28, 2012 9:12:17 PM com.couchbase.client.CouchbaseConnectionFactory checkConfigUpdate
WARNING: No reconnect required, though check requested. Current config check is 1 out of a threshold of 10.
Exception in thread "main" net.spy.memcached.OperationTimeoutException: Timeout waiting for value
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1003)
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1018)
at Main.main(Main.java:34)
Caused by: net.spy.memcached.internal.CheckedOperationTimeoutException: Timed out waiting for operation - failing node: 169.254.20.219/169.254.20.219:11210
at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:93)
at net.spy.memcached.internal.GetFuture.get(GetFuture.java:62)
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:997)
... 2 more

[JCBC-69] Java 1.1DP zip is missing dependent jars

Fri, 29 Jun 2012 17:43:47 -0500

Java .zip distribution seems to be missing httpcore-4.1.1.jar,httpcore-nio-4.1.1.jar.

[JCBC-68] Query.copy() copies Key into EndkeyDocID

Fri, 29 Jun 2012 14:26:59 -0500

The bug causes all query results are not as expected: in every case "key" argument is changed to "EndkeyDocID".

My proposed patch:

$
diff --git a/src/main/java/com/couchbase/client/protocol/views/Query.java b/src/main/java/com/couchbase/client/protocol/views/Query.java
index fca7ccf..3a019a0 100644
--- a/src/main/java/com/couchbase/client/protocol/views/Query.java
+++ b/src/main/java/com/couchbase/client/protocol/views/Query.java
@@ -174,7 +174,7 @@ public class Query {
       query.setInclusiveEnd(((Boolean)args.get(INCLUSIVEEND)).booleanValue());
     }
     if (args.containsKey(KEY)) {
- query.setEndkeyDocID(((String)args.get(KEY)));
+ query.setKey(((String)args.get(KEY)));
     }
     if (args.containsKey(LIMIT)) {
       query.setLimit(((Integer)args.get(LIMIT)).intValue());
$

[JCBC-54] configuration checks can overwhelm application code if run without a threshold

Mon, 30 Jul 2012 16:22:30 -0500

With changes introduced in 1.0.2, there are frequent configuration checks. They are, unfortunately, too frequent and can overload a system if there there are a large number of requests. Also, ConfigurationProviders are not being shut down gracefully.

[JCBC-49] Query limit does not work with paged queries

Tue, 18 Sep 2012 12:42:16 -0500

Query limit property does not work with paged queries. Paginator overwrites the limit with the page size without saving the original and a counter is not kept.

[JCBC-45] asyncGetAndLock returns the same value when a lock is refused and when a key is not found

Sun, 3 Jun 2012 22:00:04 -0500

This report is re: asyncGetAndLock method in the java client.

From the current implementation of asyncGetAndLock , it is impossible to tell the difference between
- a value that doesn't exist(& should be added) and
- a value that exists, but is locked by another client.

In both cases, you get this:
CASValue<T>(-1, null);

which customer opines is pretty non-useful in the cases where you want to decide whether to try again or move on to an add.

Suggestion from the customer is:

Add the CasGetStatus class which has additional information about the failure type (attached), and modify CouchbaseClient.java to create and return that class (diff attached).

Attached files:
1) CASGetStatus.java
2) couchbasediff.txt

[JCBC-44] ViewFuture and HttpFuture may throw NPE

Sun, 3 Jun 2012 20:55:22 -0500

ViewFuture and HttpFuture have duplicate "wait and check" code to set the status. There is no check for null op for the case op.isCancelled()

[JCBC-39] release 1.0.3 and later should depend on spymemcached 2.8.2

Tue, 31 Jul 2012 00:40:33 -0500

Inadvertently, 1.0.2 was built dependent on 2.8.1 but with maven description saying 2.8.0. We should just update to the latest.

[JCBC-36] document getl, unlock

Thu, 31 Jan 2013 23:38:09 -0600

A user reports that getl and unlock are not documented. They should be.

[JCBC-34] Allow modifying 1000 timeout threshold

Thu, 19 Apr 2012 01:13:31 -0500

Currently the number of consecutive timeouts before marking a node as failed is hardcoded to 1000.

This should be tunable.

[JCBC-30] document warning on not-my-vbucket errors

Wed, 27 Feb 2013 13:10:00 -0600

During rebalance, WARNING level errors such as
WARN com.couchbase.client.CouchbaseConnection: Reschedule read op due to NOT_MY_VBUCKET error: Cmd: 0 Opaque: 460 Key: membase-test-key-24
can come up. These are safe to ignore, as long as they're small in number and do not persist for a long period of time.

This needs to be documented somewhere in the manuals.

[JCBC-25] support errors on views

Fri, 14 Sep 2012 19:23:14 -0500

Views now have some options on capturing errors and stopping on errors as documented here:
http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-views-writing-querying-errorcontrol.html

The client needs to support these.

[JCBC-24] cannot do group_level without group

Fri, 1 Jun 2012 19:13:19 -0500

Currently, it's not possible to do group_level without group and that's a problem because one overrides the other.

See http://www.couchbase.com/forums/thread/couchbase-20-setting-grouplevel-view-queries-java-api

[JCBC-23] Implement Gson into couchbase client

Mon, 16 Jul 2012 12:43:44 -0500

Having object to json mapping would be nice.

[JCBC-13] Incorrect VBucket Hashing due to inverted bucket check (Couchbase/Membase vs. spymemcached)

Mon, 6 Feb 2012 12:40:42 -0600

Incorrect VBucket Hashing due to inverted bucket check (Couchbase/Membase vs. spymemcached)

[JCBC-194] TAP client within spymemcached does not get all items from cluster

Wed, 19 Dec 2012 11:26:29 -0600

From the customer:

TapClient client = new TapClient(baseURIs, "default", "default", "");

            Operation op = client.tapDump("test tap client");

            while (client.hasMoreMessages()) {
                ResponseMessage message = client.getNextMessage();
                if (message != null) {
                    System.out.println(message.getKey());
                }
            }

I made the client point to a cluster that has 60 M records . The client printed out about 8M and stopped without error, when I tried again it stopped at 10M.

[JCBC-195] Failed operations during rebalance with "not my vbucket"

Wed, 19 Dec 2012 11:25:27 -0600

From the customer:

I made the client write a million records when the rebalancing was happening when it finished the client had written only 920000 records . I checked the operation status and message from the future, future.isSuccess() returned false and "I'm not responsible for this vbucket" was the message. Let me know if you need more info.

[JCBC-7] getting started is also on the web page

Mon, 6 Feb 2012 12:31:44 -0600

getting started is also on the web page

[JCBC-8] getting started screencast is available

Mon, 6 Feb 2012 12:31:44 -0600

getting started screencast is available

[JCBC-6] getting started guide needed

Mon, 6 Feb 2012 12:31:44 -0600

getting started guide needed

[JCBC-9] tutorial chapter is complete

Mon, 6 Feb 2012 12:51:35 -0600

tutorial chapter is complete

[JCBC-10] API reference is complete

Mon, 6 Feb 2012 12:31:44 -0600

API reference is complete

[JCBC-4] building shippable artifacts under CI

Tue, 26 Mar 2013 07:11:29 -0500

This is simply generating the JAR files under CI.

[JCBC-1] ensure building under CI

Tue, 26 Mar 2013 07:10:50 -0500

ensure building under CI

[JCBC-2] running unit tests under CI

Duplicate — Thu, 31 Jan 2013 09:19:59 -0600

running unit tests under CI

[JCBC-146] Paginator should support reduced views.

Dependency — Wed, 8 May 2013 05:26:23 -0500

Paginator should support reduced views.

[JCBC-268] ReplicateTo.ZERO+PersistTo.ZERO should be handled specially so as not to impact performance

Wed, 8 May 2013 10:27:21 -0500

When testing the durability constraints with ZERO for both replicate and persist, there is a noticeable drop in throughput due to the extra call to the server to check for these constraints.

Intuitively, since this is a "single" API that hides the functionality from the user, the user expects that supplying ZERO for both of these options should be the same speed as not supplying them at all.

[JCBC-288] Query.setKey() does not parse properly string that starts with number but contains letter

Fri, 10 May 2013 01:28:49 -0500

When a query is made with the setKey and this key starts with number but contains chars, our Query parser transforms this as Number, for example

"123ABC" will be sent as key=123

Note that the complex key and setKeys() are working properly.

[JCBC-297] Release Java Client 1.1.6

Fri, 10 May 2013 14:05:19 -0500

Release the Java Client 1.1.6

[JCBC-265] ConfigurationProviderMock fails during test.

Dependency — Tue, 12 Mar 2013 05:52:45 -0500

Hi Michael,

This issue is reproducible as below :

java.lang.AssertionError: Could not verify the init of a memcache bucket
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.assertTrue(Assert.java:43)
at com.couchbase.client.CouchbaseClientMemcachedBucketTest.testMemcacheBucketInitialization(CouchbaseClientMemcachedBucketTest.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

[JCBC-213] IllegalArgumentException when calling vBucket-related methods

Fri, 18 Jan 2013 01:30:09 -0600

Getting an "TODO: Implement this" when calling CouchbaseConnectionFactory.getVbucketConfig().getVbucketsCount() and the bucket is a memcached bucket.

While the failure is understandable, the exception thrown should be different.

I'm not sure if this has always been the behavior or it was introduced into the 1.1.x version.

the file from which the exception is thrown;

src/main/java/com/couchbase/client/vbucket/config/CacheConfig.java

Looking at the commit log on that file, it seems to be some older "configuration" class - and doesn't seem to have changed significantly since.

[JCBC-200] heading too specific "Set operations with Observe"

Fri, 4 Jan 2013 10:38:49 -0600

The heading for this page is too narrow: "Set Operations with Observe". It would be better to call it "Store Operations with Observe".

[JCBC-181] Misleading exception when replica server not found

Duplicate — Thu, 31 Jan 2013 10:00:19 -0600

If the number of Couchbase servers is not enough to provide the required number of replicas (e.g. when installing a stand-alone server and forgetting to uncheck the 'Enable replicas' option), observe throws an ArrayIndexOutOfBoundsException. An exception with a more descriptive name would indicate the error cause more clearly.

An example stack trace:

ArrayIndexOutOfBoundsException: -1
     java.util.ArrayList.elementData(ArrayList.java:371)
     java.util.ArrayList.get(ArrayList.java:384)
     com.couchbase.client.vbucket.config.DefaultConfig.getServer(DefaultConfig.java:81)
     com.couchbase.client.vbucket.VBucketNodeLocator.getServerByIndex(VBucketNodeLocator.java:112)
     com.couchbase.client.CouchbaseClient.observe(CouchbaseClient.java:1621)
     com.couchbase.client.CouchbaseClient.observePoll(CouchbaseClient.java:1750)
     com.couchbase.client.CouchbaseClient.set(CouchbaseClient.java:1199)
     ...

[JCBC-179] Java Client's Manual 1.1-Tutorial issue

Dependency — Mon, 17 Dec 2012 01:22:17 -0600

Took the latest checkin of the tutorial example from https://github.com/couchbaselabs/beersample-java
Packaged the maven project.
jquery.min.js is not getting compiled.

[JCBC-163] test failures in TAP

Thu, 6 Dec 2012 03:05:58 -0600

In current test execution scenarios, the TAP tests are failing for an unknown reason.

testBackfill
java.lang.AssertionError
at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:103)
at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:143)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:642)
at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:301)
at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:739)
at com.couchbase.client.TapTest.testBackfill(TapTest.java:80)

testTapDump
java.lang.AssertionError
at com.couchbase.client.vbucket.VBucketNodeLocator.getPrimary(VBucketNodeLocator.java:103)
at com.couchbase.client.CouchbaseConnection.addOperation(CouchbaseConnection.java:143)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:642)
at net.spy.memcached.MemcachedClient.asyncStore(MemcachedClient.java:301)
at net.spy.memcached.MemcachedClient.set(MemcachedClient.java:739)
at com.couchbase.client.TapTest.testTapDump(TapTest.java:103)

[JCBC-120] NPE when connecting to memcached bucket without configured password

Thu, 31 Jan 2013 23:37:20 -0600

2012-09-28 09:53:31.562 INFO com.couchbase.client.CouchbaseMemcachedConnection: Added {QA sa=/10.3.3.135:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
java.lang.NullPointerException
        at net.spy.memcached.auth.PlainCallbackHandler.<init>(PlainCallbackHandler.java:50)
        at com.couchbase.client.CouchbaseConnectionFactory.getAuthDescriptor(CouchbaseConnectionFactory.java:187)
        at net.spy.memcached.MemcachedClient.<init>(MemcachedClient.java:197)
        at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:230)
        at com.couchbase.client.CouchbaseClient.<init>(CouchbaseClient.java:200)
        at com.couchbase.cbc.App.main(App.java:69)

-- SNIPPET --

        CouchbaseClient cli = null;
        LinkedList<URI> uriList = new LinkedList<URI>();

        try {
            uriList.add(new URI("http://" + options.hostname + "/pools"));
            cli = new CouchbaseClient(
                    uriList,
                    options.bucket, options.username, options.password);
        } catch (Exception ex) {
            ex.printStackTrace();
            System.exit(-1);
        }

[JCBC-98] Multiple exceptions thrown on Shutdown()

Mon, 3 Dec 2012 05:36:19 -0600

The following exceptions are thrown when a CouchbaseClient calls shutdown()

java.io.IOException: No IO while shut down
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:201)
at com.couchbase.client.CouchbaseConnection.run(CouchbaseConnection.java:230)

This can easily be seen when logging is enabled.

[JCBC-62] StringUtils.join

Thu, 14 Jun 2012 23:49:48 -0500

net.spy.memcached.util.StringUtils.join does not implement standard join function

pseudocode:
e.g. join(["a", "b", "c"], ",") should output "a,b,c"
the actual output is "a,b,c,"

[JCBC-58] The get() function in HTTPFuture and ViewFuture contain duplicate code

Mon, 3 Dec 2012 05:36:20 -0600

See ~~JCBC-44~~ for more info.

[JCBC-57] Tutorial output does not match description

Thu, 7 Jun 2012 13:54:59 -0500

Section 1.3 of documentation:

Documented output above the following paragraph shows "Synchronous Get Suceeded: Hello World!"

Much of this output is logging statements produced by the client library, to inform you of what's going on inside the
client library to help you diagnose issues. It says that a connection to Couchbase was added and that the connection state
changed. Then the code shows that the key spoon did not exist in Couchbase which is why the Synchronous Get failed.

[JCBC-55] client.replace docs do not agree with codebase

Fri, 14 Sep 2012 12:31:55 -0500

http://www.couchbase.com/docs/couchbase-sdk-java-1.1/api-reference-summary.html

client.replace arguments are key, expiry, object, but are indicated as key, object, expiry

Not splitting key/value makes more sense as the API will be more consistent in JVM languages that allow default values, e.g. replace(key, object, expiry=0), but the rest of the API uses key, expiry, object order so splitting makes sense to be consistent in the Java version.

[JCBC-50] Tutorial code improvements

Thu, 30 Aug 2012 08:05:39 -0500

http://www.couchbase.com/docs/couchbase-sdk-java-1.1/using-vbuckets.html
http://www.couchbase.com/docs/couchbase-sdk-java-1.1/complete-tutorial-code.html
http://www.couchbase.com/docs/couchbase-sdk-java-1.1/complete-tutorial-code-with-views.html

* both reference "rags" bucket and the first two use "password" instead of the default empty string.

* The last two have extraneous System.exit(0)

* It is not clear how the vBuckets initialization is different from the other client initialization. From v1.8 docs section 1.3.5, vBuckets are not user accessible. It is unclear why there would be special code to connect to them

* The example output is missing from the vBuckets page

* capitalization of vBuckets should be consistent

http://www.couchbase.com/docs/couchbase-sdk-java-1.1/connecting.html

* There is no fallbackAddress variable
* The fallback variable lines should be added *after* the third line

[JCBC-43] VBucketNodeLocator inner classes should be static

Fri, 15 Jun 2012 13:24:26 -0500

TotalConfig and NullIterator don't depend on VBucketNodeLocator so should be static.

Should NullIterator be private and getSequence final?

[JCBC-42] FIleInputStream in ConnectionClient is not closed

Fri, 1 Jun 2012 19:14:45 -0500

The FileInputStream for cbclient.properties is never closed.
Instead of ClassLoader.getSystemResource use:

InputStream propStream = null
try {
   propStream = ClassLoader.getSystemResourceAsStream("cbclient.properties")
   if (propStream != null) {
       properties.load(propStream)
   } else {
       // handle properties not found
   }
   viewmode = properties.getProperty("viewmode");
catch (IOException ex) {
  // handle real exception
} finally {
  try {
  if (propStream != null) propStream.close()
} catch (IOException ex)
  // ignore
}
}

More parens, but no leaks and missing properties is handled normally not as an exception

[JCBC-37] Missing documentation for CouchbaseConnectionFactoryBuilder()

Fri, 14 Sep 2012 17:36:04 -0500

http://www.couchbase.com/docs/couchbase-sdk-java-1.1/connecting.html

Option to use CouchbaseConnectionFactoryBuilder to set options and create a ConnectionFactoryBuilder is not listed. The configuration parameters for the builder are also no listed.

"Connecting to the Server" sounds more idiomatic

[JCBC-177] support a single null in a view query

Wed, 8 May 2013 06:01:27 -0500

In ComplexKeyTest.java, there is a disabled test for handling a ComplexKey.of((Object[]) null); since it would NPE. This should be fixed.

It's not that likely someone will start a query with null, but it is possible.

[JCBC-284] Create new methods (set/add/update) with no ttl (to be persisted "for ever" by default)

Fri, 10 May 2013 01:28:07 -0500

To improve the developer experience it is better to allow developers to do a
client.set("K","V")

and this will be equivalent of a 0 TTL.

This should be done for set,add,replace (all methods with a TTL)

[JCBC-293] Clarification/Agreement on Javadocs Build Workaround

Duplicate — Tue, 14 May 2013 12:44:02 -0500

At this point, Phil needs clarification: if his workaround is OK, and clarify spymemcached is ours + what version we need to use....

Please assign to him to apply the workaround after you get a change to clarify.

-----------

Sent via email by Dipti 4/31.

-----------------------

Background:

Hi Wayne,

It is on jenkins@ubu-1702.hq.couchbase.com. You can access it on with the QA key, QAkey.pem.

The ANT file is supposed to build javadocs and rdocs and the problem we are encountering is that we had included third parties libraries (spymemcached) and it the latest javadoc generation they were not included.

Thanks,

Karen

-------

Wayne assigne to Phil and Phil investigates for several hours

----------------

From Phil:

From: Philip Labee <Philip@couchbase.com>
Date: Friday, April 19, 2013 2:07 PM
To: Matt Ingenthron <matt@couchbase.com>, Michael Nitschinger <Michael.Nitschinger@couchbase.com>
Cc: Karen Zeller <karen.zeller@couchbase.com>, Wayne Siu <Wayne@couchbase.com>
Subject: building javadocs for couchbase-java-client

Karen and I are following the directions for building the javadocs but it looks like these instructions are incomplete. Specifically they say to create a clean clone of couchbase-java-client and to run "ant docs" there, but the problem is that it only generates docs for our code, and misses all the net.spy.memcached docs because the spy.memcached source files are not in the build tree.

I could easily clone the spy.memcached source files into ~jenkins and then symlink the src/main/java/net files into the sr/main/java directory of the client build dir, but there's no evidence that this is how it was done before. If you know how this was done in previous releases which do include the docs for spy.memcached, let me know and we'll update the instructions and generate a complete set of javadocs. If we don't discover a known solution we'll proceed with the cloning and the symlinking. If we don't want to include third-party docs in our doc-set then there's nothing more to do.

net.spy.memcached docs included: http://www.couchbase.com/autodocs/couchbase-java-client-1.1.4c/index.html

Not included: http://www.couchbase.com/autodocs/couchbase-java-client-1.1.5/index.html

--Phil

[JCBC-56] Java client is marked GA

Fri, 8 Jun 2012 09:59:26 -0500

A.1. Release Notes for 1.1DP Couchbase Client Library Java GA (16 March 2012)

GA should be dropped until actual GA release
For future releases may read better as: Couchbase Java Client Library 1.1 DP (16 March 2012)
updated for actual release number and date