Details
-
Task
-
Resolution: Won't Fix
-
Critical
-
1.2.2, 1.2.8
Description
From the following thread: https://groups.google.com/forum/#!topic/couchbase-8091/coADcepVnV4
>>>>>
Re: Backup is running to 200.7% after crash (was: Re: [Team 8091] Couchbase server crashed during minimal load test)
Ok everyone, blast from the past. We are about to launch 2.2 of the same app that was experiencing index out of range errors accessing a view. We have continued to see this error show up during minimal as well as heavy load testing. We have multiple views and for some reason this one view causes us problems. It's use is almost identical to another that hasn't error and is access immediately before this failing view.
The content they return is different though. The error, for simplicity sake is pasted below:
System.ArgumentOutOfRangeExceptionIndex was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at Couchbase.CouchbaseClient.Couchbase.IHttpClientLocator.Locate(String designDocument)
at Couchbase.CouchbaseViewHandler.GetResponse(IDictionary`2 viewParams)
at Couchbase.CouchbaseViewHandler.<TransformResults>d__0`1.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ###.Framework.Tracking.PageVisitLogger.GetResourceAccesses(String userId)
at ###.Framework.GlobalApplication.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
For the 2.1 release that started this thread, we identified issues with the .NET 1.2.6 and had to go back to 1.2.0. For this 2.2 release I tried 1.2.7 and 1.2.8 and still experienced the issue so was not able to upgrade still. The issue we have run into is documented in this thread so I'm not going to rehash it here. I even provided diagnostics to Couchbase for troubleshooting purposes.
Two things:
Is there an ETA on when this issue will be resolved?
What might cause this exception for just one view?
Thanks!
-K