[infinispan-issues] [JBoss JIRA] (ISPN-5891) IntegrationTest.testConcurrentETagChanges always fails

[Dan Berindei (JIRA)]

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

Dan Berindei updated ISPN-5891:
-------------------------------
    Description: 
The test always fails since the ISPN-5857 fix was integrated.

When executing a {{PUT}} operation, the REST server always looks up the previous value,  and if it exists, it executes a {{cache.replace(k, old, new)}} cache operation instead of a regular push. But the cache is configured with {{value-equivalence=AnyEquivalence}}, so the replace fails if the REST server is not the primary owner.

It was successful before the ISPN-5857 fix only because the server was the primary owner of the key, and then only because {{ValueMatcher.equal()}} checks identity first.

  was:
The test always fails since the ISPN-5857 fix was integrated.

When executing a {{PUT}} operation, the REST server always looks up the previous value,  and if it exists, it executes a {{cache.replace(k, old, new)}} cache operation instead of a regular push. But the cache is configured with {{AnyEquivalence}}, so the replace fails if the REST server is not the primary owner.

It was successful before the ISPN-5857 fix only because the server was the primary owner of the key, and then only because {{ValueMatcher.equal()}} checks identity first.



> IntegrationTest.testConcurrentETagChanges always fails
> ------------------------------------------------------
>
>                 Key: ISPN-5891
>                 URL: https://issues.jboss.org/browse/ISPN-5891
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Server, Test Suite - Server
>    Affects Versions: 8.1.0.Alpha2
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Blocker
>              Labels: testsuite_stability
>             Fix For: 8.1.0.Beta1
>
>
> The test always fails since the ISPN-5857 fix was integrated.
> When executing a {{PUT}} operation, the REST server always looks up the previous value,  and if it exists, it executes a {{cache.replace(k, old, new)}} cache operation instead of a regular push. But the cache is configured with {{value-equivalence=AnyEquivalence}}, so the replace fails if the REST server is not the primary owner.
> It was successful before the ISPN-5857 fix only because the server was the primary owner of the key, and then only because {{ValueMatcher.equal()}} checks identity first.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)