Bug 745824 (EDG-72) - memcached server module delete command processing logic issue
Summary: memcached server module delete command processing logic issue
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-72
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-72
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-17 12:17 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-23 08:40:28 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Michal Linhard 2010-11-17 12:17:12 UTC
project_key: EDG

The text protocol processing logic regarding delete command doesn't allow for command pipelining:

$ echo -e "delete a\r\ndelete a\r" | nc localhost 11211
CLIENT_ERROR org.infinispan.server.core.ServerException: java.io.StreamCorruptedException: Unable to parse noreply optional argument

the logic is as follows

1. read header "delete "
2. read key "a\r\n"
3. read parameters READS ERRONEOUSLY NEXT COMMAND: "delete a\r\n"

when sending one command only this is ok
$ echo -e "delete a\r" | nc localhost 11211
NOT_FOUND

because read parameters in step 3 just returns line ""
but makes trouble when delete command appears in the middle of the command input stream.

Comment 1 Galder Zamarreño 2010-11-18 10:08:47 UTC
Link: Added: This issue depends ISPN-781



Note You need to log in before you can comment on or make changes to this bug.