I am continuously getting the error through the dotnet client "Object synchronization method was called from an unsynchronized block of code" when the load on the memcache server increases.
I have set the following default value for memcached connections:
SockIOPool pool = SockIOPool.GetInstance();
pool.SetServers(serverlist);
This library has kind of been abandoned. Have you looked into AppFabric
caching (formerly Velocity) if you're on the .NET stack? It's full
featured and supported by MSFT.
On Fri, May 31, 2013 at 9:21 AM, Shikhar Maheshwari <icoshikhar@users.sf.net
wrote:
Hi,
I am continuously getting the error through the dotnet client "Object
synchronization method was called from an unsynchronized block of code"
when the load on the memcache server increases.
I have set the following default value for memcached connections:
SockIOPool pool = SockIOPool.GetInstance();
pool.SetServers(serverlist);
Why does MemCached does not close the connection on it's own after the operation has been performed. What is the alternative client library that you would suggest for proper functioning - BeIT or Enyim or some other...
Requesting prompt response...
With Regards,
Shikhar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry not to be of much help, but I haven't looked at this code base in a
very long time. For the .NET world you're probably better off using the
AppFabric cache that is more native and supported by MSFT for distributed
caching. Otherwise if you're not keen on that I know that the
StackOverflow team uses Redis for their caching scheme so that solution is
well supported by the community. I'm just not very familiar with the
projects you mentioned.
On Mon, Jun 10, 2013 at 5:41 AM, Shikhar Maheshwari <icoshikhar@users.sf.net
wrote:
Hi Tim,
Thanks for the reply.
Why does MemCached does not close the connection on it's own after the
operation has been performed. What is the alternative client library that
you would suggest for proper functioning - BeIT or Enyim or some other...
Hi,
I am continuously getting the error through the dotnet client "Object synchronization method was called from an unsynchronized block of code" when the load on the memcache server increases.
I have set the following default value for memcached connections:
SockIOPool pool = SockIOPool.GetInstance();
pool.SetServers(serverlist);
Am I missing something. Please help.
This library has kind of been abandoned. Have you looked into AppFabric
caching (formerly Velocity) if you're on the .NET stack? It's full
featured and supported by MSFT.
On Fri, May 31, 2013 at 9:21 AM, Shikhar Maheshwari <icoshikhar@users.sf.net
Hi Tim,
Thanks for the reply.
Why does MemCached does not close the connection on it's own after the operation has been performed. What is the alternative client library that you would suggest for proper functioning - BeIT or Enyim or some other...
Requesting prompt response...
With Regards,
Shikhar
Hi Shikhar,
Sorry not to be of much help, but I haven't looked at this code base in a
very long time. For the .NET world you're probably better off using the
AppFabric cache that is more native and supported by MSFT for distributed
caching. Otherwise if you're not keen on that I know that the
StackOverflow team uses Redis for their caching scheme so that solution is
well supported by the community. I'm just not very familiar with the
projects you mentioned.
On Mon, Jun 10, 2013 at 5:41 AM, Shikhar Maheshwari <icoshikhar@users.sf.net