Exchange fetchAndRemove sometimes returns null
Bug #912514 reported by
Peter Beaman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Akiban Persistit |
Fix Released
|
Medium
|
Peter Beaman | ||
Bug Description
PersistitMapStress1 fails intermittently with messages like this:
Finished unit=#1 PersistitMapStress test=PersistitM
8036 Failed test unit=#1 PersistitMapStress test=PersistitM
value not expected to be null
I didn't track down the responsible code, but I'm pretty sure the contents of _spareValue have been mangled.
Since akiban-server does not use this method the bug is no more than medium priority. But it does need to be fixed before akiban-persistit is released as a standalone library.
Related branches
lp:~nwilliams/akiban-persistit/fix_912514_fetchAndRemove_2
- Peter Beaman: Approve
-
Diff: 436 lines (+185/-56)2 files modifiedsrc/main/java/com/persistit/Exchange.java (+71/-56)
src/test/java/com/persistit/Bug912514Test.java (+114/-0)
lp:~pbeaman/akiban-persistit/fix_912514_again
- Akiban Build User: Needs Fixing
- Nathan Williams: Approve
-
Diff: 111 lines (+47/-2)4 files modifiedsrc/main/java/com/persistit/Exchange.java (+2/-2)
src/main/java/com/persistit/Persistit.java (+1/-0)
src/test/java/com/persistit/ConfigurationTest.java (+8/-0)
src/test/java/com/persistit/unit/ExchangeTest.java (+36/-0)
| Changed in akiban-persistit: | |
| status: | Confirmed → Fix Committed |
| Changed in akiban-persistit: | |
| milestone: | none → 3.1.0 |
| assignee: | nobody → Peter Beaman (pbeaman) |
| Changed in akiban-persistit: | |
| milestone: | 3.1.0 → 3.1.1 |
| Changed in akiban-persistit: | |
| status: | Fix Committed → Fix Released |
| visibility: | private → public |
To post a comment you must log in.
