#15 precedessor's successor not set immediately

1.0.5
open
nobody
5
2012-11-05
2012-11-05
No

If we got the right predecessor and successor the first time, the predecessor is not immediately notified.

So I added an extra notification after predecessorSet = true; and it seems to work.

predecessorSet = true;
refs.get(0).notify(localNode);

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks