[infinispan-issues] [JBoss JIRA] (ISPN-2052) Removing non-existent keys with force return previous value fails with Hot Rod client

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-2052:
-----------------------------------

              Status: Pull Request Sent  (was: Coding In Progress)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/1125

    
> Removing non-existent keys with force return previous value fails with Hot Rod client
> -------------------------------------------------------------------------------------
>
>                 Key: ISPN-2052
>                 URL: https://issues.jboss.org/browse/ISPN-2052
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 5.1.4.FINAL, 5.1.5.CR1
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.5.FINAL
>
>
> While investigating http://goo.gl/4t4gQ, I've come across an issue in the Hot Rod client. The protocol (https://docs.jboss.org/author/x/eICQ) indicates that the remove response consists of:
> {quote}If ForceReturnPreviousValue has been passed, remove response will contain previous value (including value length) for that key. If the key does not exist or previous was null, value length would be 0. Otherwise, if no ForceReturnPreviousValue was sent, the response would be empty.{quote}
> The problem is that the client does not read the last length byte if the key is not present, after a remove for a key with force return previous value that does not exists, if you do any operation, you'll see:
> {code}org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x0
> 	at org.infinispan.client.hotrod.impl.protocol.Codec10.readHeader(Codec10.java:92){code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira