[infinispan-issues] [JBoss JIRA] (ISPN-3270) Hotrod clients removeWithVersion doesn't work with replicated cache

[Jakub Markos (JIRA)]

Jakub Markos created ISPN-3270:
----------------------------------

             Summary: Hotrod clients removeWithVersion doesn't work with replicated cache
                 Key: ISPN-3270
                 URL: https://issues.jboss.org/browse/ISPN-3270
             Project: Infinispan
          Issue Type: Bug
          Components: Remote protocols
            Reporter: Jakub Markos
            Assignee: Galder Zamarreño


I have a cluster of 2 latest infinispan servers (6.0.0-SNAPSHOT) with the following container configuration:
{code:xml}<cache-container name="default" default-cache="default" listener-executor="infinispan-listener">
    <transport stack="udp" executor="infinispan-transport" lock-timeout="240000"/>
    <replicated-cache name="default" start="EAGER" mode="SYNC" batching="false" remote-timeout="60000">
        <transaction mode="NONE"/>
        <state-transfer enabled="true" timeout="60000"/>
    </replicated-cache>
</cache-container>
{code}

Running this code:

{code}    remoteCache = remoteCacheManager.getCache();
    remoteCache.clear();
    assertFalse(remoteCache.removeWithVersion("aKey", 12321212l));
    remoteCache.put("aKey", "aValue");
    VersionedValue valueBinary = remoteCache.getVersioned("aKey");
    System.out.println("value = " + valueBinary.getValue());
    System.out.println("version = " + valueBinary.getVersion());
    System.out.println(remoteCache.removeWithVersion("aKey",valueBinary.getVersion()));
    valueBinary = remoteCache.getVersioned("aKey");
    System.out.println("value = " + valueBinary.getValue());
    System.out.println("version = " + valueBinary.getVersion());
{code}

results most of the time in (and the other times the removeWithVersion returns false)
{quote}
value = aValue
version = 281483566645249
true
value = aValue
version = 281483566645249
{quote}

The command works with distributed/local cache.




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira