Bug 1252986
| Summary: | putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Shay Matasaro <smatasar> |
| Component: | Infinispan | Assignee: | Galder Zamarreño <galder.zamarreno> |
| Status: | VERIFIED --- | QA Contact: | Martin Gencur <mgencur> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5.0 | CC: | chuffman, jdg-bugs, pzapataf |
| Target Milestone: | CR1 | ||
| Target Release: | 6.5.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The call to <methodname>putIfAbsentAsync</methodname> on a remote HotRod client and using <parameter>withFlags(Flag.FORCE_RETURN_VALUE)</parameter> did not work as expected. The previous value was not returned as expected unless the flag was also configured in HotRod client properties file.
This issue is resolved as of Red Hat JBoss Data Grid 6.5.1.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-5677 to Coding In Progress Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-5677 to Reopened Gustavo Fernandes <gustavo> updated the status of jira ISPN-5677 to Coding In Progress |
given the following HR client code NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); System.out.println(f1.get(10,TimeUnit.MINUTES)); NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); System.out.println(f2.get(10,TimeUnit.MINUTES)); both prints print null, where the second one should print "1" only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work