[infinispan-issues] [JBoss JIRA] Commented: (ISPN-781) Memcached pipelined delete messages wrongly processed

[Galder Zamarreño (JIRA)]

    [ https://jira.jboss.org/browse/ISPN-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564648#comment-12564648 ] 

Galder Zamarreño commented on ISPN-781:
---------------------------------------

https://github.com/infinispan/infinispan/pull/55
and https://github.com/infinispan/infinispan/pull/56

> Memcached pipelined delete messages wrongly processed
> -----------------------------------------------------
>
>                 Key: ISPN-781
>                 URL: https://jira.jboss.org/browse/ISPN-781
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 4.1.0.Final, 4.2.0.BETA1
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 4.2.0.CR1, 4.2.0.Final
>
>
> The code incorrectly detects the optional, unsupported, noreply parameter.
> From Michal:
> "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."

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira