Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISPN-5477 Too agressive unboxing leading to wrong L1 returns #3476

Closed
wants to merge 1 commit into from

Conversation

galderz
Copy link
Member

@galderz galderz commented May 18, 2015

https://issues.jboss.org/browse/ISPN-5477

  • Unboxing of entries for external client consumption should only happen when commands are local, since remote commands come from internal clustering.

@galderz galderz added this to the 7.2.2.Final milestone May 18, 2015
CompatibilityCacheFactory.killCacheFactories(cacheFactory1, cacheFactory2);
}

// public void testHotRodPutInNonOwner() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we adding this back in? If not we can remove the SplitMagicKey class it seems.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seems to be an overlap in functionality between getSplitIntKeyForServer and SplitMagicKey anyway...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover stuff, I'll clean it up and update.

* Unboxing of entries for external client consumption should only
happen when commands are local, since remote commands come from
internal clustering.
@galderz
Copy link
Member Author

galderz commented May 22, 2015

Updated

@danberindei
Copy link
Member

Integrated, thanks Galder!

@danberindei
Copy link
Member

And now in 7.2.x as well.

@anistor
Copy link
Member

anistor commented May 23, 2015

@danberindei @galderz I'm not sure what the problem is but it seems these changes cause the tests to hang on master. Reverting them fixes the problem.

@galderz
Copy link
Member Author

galderz commented May 28, 2015

Two PRs have been sent to fix this: #3501 and #3503

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants