[SPY-88] OperationState as tracked in BaseOperationImpl should be volatile Created: 21/May/12 Updated: 29/May/13 |
|
| Status: | Reopened |
| Project: | Spymemcached Java Client |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | .next |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Matt Ingenthron |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Since the OperationState is accessed by multiple threads, there can be a coherency issue if the application code is trying to reference the OperationState after an OperationFuture has completed, but a previous value of the OperationState is not seen on the thread of the application blocking on that OperationFuture.
|
| Comments |
| Comment by Matt Ingenthron [ 21/Jul/12 ] |
| Found that the fix here was introducing test failures in multigets. The problem isn't with the fix posted in http://review.couchbase.org/#change,16255 but rather that it now correctly asserts. |
| Comment by Michael Nitschinger [ 29/May/13 ] |
| This is also quite old, does that mean its already fixed Matt? |