Spymemcached Java Client

OperationState as tracked in BaseOperationImpl should be volatile

Details

  • Type: Bug Bug
  • Status: Reopened Reopened
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Labels:
    None

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.

Activity

Ascending order - Click to sort in descending order
Matt Ingenthron made changes -
Field Original Value New Value
Assignee Raghavan Srinivas [ rags ] Matt Ingenthron [ ingenthr ]
Matt Ingenthron made changes -
Project Couchbase Java Client [ 10080 ] Spymemcached Java Client [ 10047 ]
Key JCBC-52 SPY-88
Mike Wiederhold made changes -
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Matt Ingenthron made changes -
Resolution Fixed [ 1 ]
Status Resolved [ 5 ] Reopened [ 4 ]

People

  • Assignee:
    Matt Ingenthron
    Reporter:
    Matt Ingenthron
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: