search

3nity-sol / spymemcached

Automatically exported from code.google.com/p/spymemcached
0 stars 0 forks source link

Error Storing Strings larger than 1 mb in client versions 2.8.0 to 2.8.4 #280

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi,

The set call in Memcached client fails for Strings greater than 1 mb for the 
recent client versions after 2.8.0. It works with version 2.7.3.

The set call should succeed because the String size is less than 1 mb after 
gzip compression which would be applied on the String.

I have attached an Test program.

Below is the Stack Trace:

Exception in thread "main" java.util.concurrent.ExecutionException: 
OperationException: SERVER: SERVER_ERROR object too large for cache
        at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:100)
        at net.spy.memcached.internal.OperationFuture.get(OperationFuture.java:79)
        at BigStringTest.main(BigStringTest.java:32)
Caused by: OperationException: SERVER: SERVER_ERROR object too large for cache
        at net.spy.memcached.protocol.BaseOperationImpl.handleError(BaseOperationImpl.java:164)
        at net.spy.memcached.protocol.ascii.OperationImpl.readFromBuffer(OperationImpl.java:151)
        at net.spy.memcached.MemcachedConnection.handleReads(MemcachedConnection.java:463)
        at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:380)
        at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:242)
        at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:833)

Thanks & Regards,
Suresh

Original issue reported on code.google.com by Suresh.M...@gmail.com on 14 Jun 2013 at 1:12

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by ingen...@gmail.com on 14 Jun 2013 at 4:28