-
Bug
-
Resolution: Done
-
Major
-
4.1.0.Final, 4.2.0.BETA1
-
None
-
Low
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."