http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/JCBC-134 Couchbase Java Client Exception in thread &quot;couchbase cluster resubscriber - running&quot; java.lang.IllegalArgumentException: Bucket name cannot be null and must never be re-set to a new object. <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at com.couchbase.client.vbucket.ConfigurationProviderHTTP.subscribe(ConfigurationProviderHTTP.java:240) <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at com.couchbase.client.vbucket.ConfigurationProviderHTTP.finishResubscribe(ConfigurationProviderHTTP.java:215) <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at com.couchbase.client.CouchbaseConnectionFactory$Resubscriber.run(CouchbaseConnectionFactory.java:322) <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at java.lang.Thread.run(Thread.java:679) <br/> <br/> <br/> Unfortunately I don&#39;t have a whole lot more insight into what&#39;s happening, but the stack trace might be helpful to examine.. assigning to myself until I have more info.. Got this during a swap-rebalance. I don&#39;t have any other relevant information to reproduce for now (fwiw I&#39;ve run this many times and it&#39;s the first time I&#39;m seeing it.. though I&#39;ve just seen it again on the very next run). <br/> <br/> During the second run, the cluster rebalance is actually hanging.. JCBC-134

resubscriber IllegalArgumentException during topology changes

Bug Critical Resolved Fixed Public Michael Nitschinger Mark Nunberg Fri, 19 Oct 2012 20:56:53 -0500 Wed, 23 Jan 2013 02:06:51 -0600 Wed, 23 Jan 2013 02:06:51 -0600 1.0 1.1.1 1.1.1 library 0 0 Hi Mark, <br/> <br/> can you elaborate a bit more whats going on through the test? This particular exception can come up when the java sdk tries to subcribe to a new node when the old connection is closed. I think the scenario should give us a connection to what is happening at runtime in the java sdk. <br/> <br/> Thanks, <br/> Michael I&#39;ve run the Java SDKD tests several times already and cannot reproduce this. Will re-open it if i see it again Seen again at:<br/> <br/> <a href="http://review.couchbase.org/#/c/24092/">http://review.couchbase.org/#/c/24092/</a> So as I mentioned in the bug, I closed it because I haven&#39;t seen this error. Just now, both me and Michael encountered this error while running the SDKD tests Attaching the logs for <a href="http://review.couchbase.org/#/c/24092">http://review.couchbase.org/#/c/24092</a> changeset 4 (prefixed with daschl-4-) on some test runs. <br/> <br/> Deepti is currently running the changeset against the brun cluster, expect some info in 2 hours. ./stester -i 20devcluster.ini --service ALL --svcaction RESTART --num_nodes 3 --no_fo 1 -c failover.Once --dsw_timeres 1 -d -o restart.log -C 127.0.0.1:8050 ./stester -i 20devcluster.ini -c rebalance.Once --mode out --rbcount 2 --dsw_timeres 1 -d -o rebealance_two_nodes.log -C 127.0.0.1:8050 Attaching the functional test results.<br/> This was run against a local 2.0.0 node.<br/> Pass rate is better this time - 92%.<br/> For the Hybrid tests - failures are still coming. <br/> <br/> Attaching the intermittent log. The error that seems to be problematic in the unit test logs is this one - <br/> <br/> &#39;Timeout occurred. Please note the time in the report does not reflect the time until the timeout. <br/> junit.framework.AssertionFailedError: Timeout occurred. Please note the time in the report does not reflect the time until the timeout.&#39; <br/> <br/> Most of the issues coming due to timeout. <br/> <br/> Note : that these tests were run against a local cluster. Hence, such problems should not be occurring. <br/> Merged in today, right before the 1.1.1 release. Dependency Rank 9486 Time In Status