Bug 745826 (EDG-46) - memcached server should reply with CLIENT_ERROR to negative item size on set/add
Summary: memcached server should reply with CLIENT_ERROR to negative item size on set/add
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-46
Product: JBoss Data Grid 5
Classification: JBoss
Component: Infinispan
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 5.1.0 EDG TP
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-46
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-17 17:13 UTC by Michal Linhard
Modified: 2014-03-17 04:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-26 12:04:32 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-46 0 None None None Never

Description Michal Linhard 2010-11-17 17:13:49 UTC 
project_key: EDG

we should respond with CLIENT_ERROR on negative item sizes in set/add operations.

our server:
$ echo -e "set issue70 0 0 -1\r" | nc localhost 11211
SERVER_ERROR org.infinispan.server.core.ServerException: java.lang.NegativeArraySizeException

original memcached implementation:
$ echo -e "set issue70 0 0 -1\r" | nc localhost 11212
CLIENT_ERROR bad command line format
Comment 1 Michal Linhard 2010-11-17 17:31:00 UTC 
this is kinda related:
the upper limit on item size is now given by max Integer size: 2147483647, because we parse the number as Integer.
when I try to allocate space for an item 2147483648 bytes big, it says
SERVER_ERROR org.infinispan.server.core.ServerException: java.lang.NumberFormatException: For input string: "2147483648"

which is kinda user unfriendly...
Comment 2 Galder Zamarreño 2010-11-18 10:31:49 UTC 
Link: Added: This issue depends ISPN-784
Comment 3 Galder Zamarreño 2010-11-18 10:31:49 UTC 
Link: Added: This issue depends ISPN-785
Note You need to log in before you can comment on or make changes to this bug.