Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
getOldValue() consistently returns wrong results for entryUpdated listener notifications after replace() #418
Whenever I update a value using replace() rather than put(), the oldValue in the entryUpdated listener gives the samne thing as the new value, so there's no way to get the true old value. This happens consistently every time, on Hazelcast 2.5.
Here's some sample code:
... showing that the old notification value is incorrect for replace() but correct for put()
I'd appreciate it if someone could look into this issue - it's a serious and obvious correctness bug that's really hurting our ability to use hazelcast, and the above testcase reproduces it in a very simple and consistent way so it should be relative easy to tackle