[SPY-107] logic on checking timeout per operation is incorrect Created: 08/Jan/13 Updated: 16/Jan/13 Resolved: 16/Jan/13 |
|
| Status: | Resolved |
| Project: | Spymemcached Java Client |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Matt Ingenthron |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
After seeing the IllegalArgumentException in a log, I re-thought through the series of events here.
This flag on the op is known by user threads and the IO thread. Thus it is modified in these two different ways: * operation is created and enqueued * OperationFuture is returned * .get() is called on OF **timed out** * operation is removed from input queue * elapsed time is checked **timed out** |
| Comments |
| Comment by Michael Nitschinger [ 16/Jan/13 ] |
| http://review.couchbase.org/23798 |