Windows install failing to store items
I am new to membase and having problems storing items. I have been able to write some unit tests to reliably store items but when I implement it in our application it fails after about 200 store commands. I have noticed that at the same time it fails to store items, the web console monitors stop updating.
We are using membase-server-enterprise_x86_64_18.104.22.168_setup on 64-bit Windows Server 2008. Our code is .Net 3.5 and we are using Enyim.Caching.dll version v2.0.50727.
This is a snippet of how we are using the client:
cache = New MembaseClient("default") cache.Store(Memcached.StoreMode.Set, key, newCacheItem)
This is our config (Membase is installed on the local machine):
<membase> <servers bucket="default" userName="Administrator" password="password"> <add uri="http://192.168.1.155:8091/pools/default" /> </servers> </membase>
This is the log4net output from when it fails:
Adding item to membase. key: ObjName:NormaliseStatsClass:ICBNormSnapID:23980FactorID:45UniSnapID23980LowerLt Acquiring stream from pool. 192.168.1.155:11210 Socket 53cf0c4b-5a01-46b5-98e8-892a4228f826 was reset Socket was reset. 53cf0c4b-5a01-46b5-98e8-892a4228f826 Key ObjName:StyleResearch.SRPA.Business.Objects.NormaliseStatsClass:ICBNormSnapID:23980FactorID:45UniSnapID23980LowerLt was mapped to 231 System.IO.IOException: Failed to read from the socket '192.168.1.155:11210'. Error: ? at Enyim.Caching.Memcached.PooledSocket.BasicNetworkStream.Read(Byte buffer, Int32 offset, Int32 count) at System.IO.BufferedStream.Read(Byte array, Int32 offset, Int32 count) at Enyim.Caching.Memcached.PooledSocket.Read(Byte buffer, Int32 offset, Int32 count) at Enyim.Caching.Memcached.Protocol.Binary.BinaryResponse.Read(PooledSocket socket) at Enyim.Caching.Memcached.Protocol.Binary.BinarySingleItemOperation.ReadResponse(PooledSocket socket) at Enyim.Caching.Memcached.Protocol.Operation.Enyim.Caching.Memcached.IOperation.ReadResponse(PooledSocket socket) at Enyim.Caching.Memcached.MemcachedNode.ExecuteOperation(IOperation op) Releasing socket 53cf0c4b-5a01-46b5-98e8-892a4228f826Are we alive? True Marking node 192.168.1.155:11210 as dead Node 192.168.1.155:11210 is dead. We have a standard config, so we'll recreate the node locator.Initializing the locator with the list of working nodes. Replaced the internal state. Acquiring stream from pool. 192.168.1.155:11210 Are we alive? False Replaced the internal state. Starting the recovery timer. Timer started.
Does anyone have any ideas why we are seeing this behaviour? Any help would be greatly appreciated.