Major Description
Exception Type: System.IndexOutOfRangeException
Stack trace:
at System.Collections.Generic.List`1.get_Item(Int32 index) |
at System.Linq.Enumerable.ElementAtOrDefault[TSource](IEnumerable`1 source, Int32 index) |
at Couchbase.IO.SharedConnectionPool`1.Acquire() |
at Couchbase.IO.Services.PooledIOService.Execute[T](IOperation`1 operation) |
at Couchbase.Core.Server.Send[T](IOperation`1 operation) |
Our application encounters this fairly frequently. Up to tens of thousands of times per day. The method of selecting the index of the connection doesn't seem to be working in all cases.
_connections.ElementAtOrDefault(GetIndex())
|
A comment in GetIndex() states " we don't care necessarily about thread safety..." , but that approach isn't working so well. Sometimes it gets the wrong index.
As a workaround we will retry the request.
Attachments
Activity
Jeff Morris I just checked and I was wrong about which version this affected. It's happening in 2.7.13. We were using 2.7.15 in DEV but this issue is happening on 2.7.13 in production.
It looks like NCBC-2148 was marked as fixed in 2.7.13.
Should we revert to 2.7.12?
Nathan Johnson -
This has been reported before and is related to
NCBC-2148; it has been reported that removing this commit fixes the problem. We will put out a new build 2.7.16 withNCBC-2148removed sometime in the near future. For now, I would suggest reverting to2.7.132.7.12 which is the release beforeNCBC-2148was committed.Thanks for reporting,
-Jeff