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

HA and stateful serializers: missing syncing of data #1814

Closed
ljacomet opened this issue Jan 30, 2017 · 1 comment
Closed

HA and stateful serializers: missing syncing of data #1814

ljacomet opened this issue Jan 30, 2017 · 1 comment
Assignees
Milestone

Comments

@ljacomet
Copy link
Member

Looks like we missed a feature combination in the 3.2.0 release of Ehcache. We do not sync to the passive server the content of the StateRepository we keep inside the EhcacheStateService.

This needs to be fixed in 3.2.1 and on master. Given the multi entity work that went into master, I believe this can't/shouldn't be fixed daggy.

@ljacomet
Copy link
Member Author

Upon further investigation, what gets sent to the server needs to change as well. That is specific types linked to a serialization library can only exist on the server in binary format.

@ljacomet ljacomet self-assigned this Feb 9, 2017
ljacomet added a commit to ljacomet/ehcache3 that referenced this issue Feb 9, 2017
The StateRepository provided map for a clustered cache cannot store
any Serializable type as otherwise the server will fail to
deserialize classes not on its classpath. So keys and values are
encoded to preserve usage flexibility while providing a best effort on
equality contract.
ljacomet added a commit to ljacomet/ehcache3 that referenced this issue Feb 9, 2017
The StateRepository provided map for a clustered cache cannot store
any Serializable type as otherwise the server will fail to
deserialize classes not on its classpath. So keys and values are
encoded to preserve usage flexibility while providing a best effort on
equality contract.
ljacomet added a commit to ljacomet/ehcache3 that referenced this issue Feb 9, 2017
The StateRepository provided map for a clustered cache cannot store
any Serializable type as otherwise the server will fail to
deserialize classes not on its classpath. So keys and values are
encoded to preserve usage flexibility while providing a best effort on
equality contract.
ljacomet added a commit to ljacomet/ehcache3 that referenced this issue Feb 9, 2017
The StateRepository provided map for a clustered cache cannot store
any Serializable type as otherwise the server will fail to
deserialize classes not on its classpath. So keys and values are
encoded to preserve usage flexibility while providing a best effort on
equality contract.
albinsuresh added a commit that referenced this issue Feb 10, 2017
[release/3.1] Issue #1814 StateRepository data format change
albinsuresh added a commit that referenced this issue Feb 10, 2017
[release/3.2] Issue #1814 Passive sync of state repository data
ljacomet added a commit to ljacomet/ehcache3 that referenced this issue Feb 10, 2017
Suppressing the warning as the type is used in a specific context
where exposing that byte[] is not an issue.
ljacomet added a commit to ljacomet/ehcache3 that referenced this issue Feb 10, 2017
Suppressing the warning as the type is used in a specific context
where exposing that byte[] is not an issue.
albinsuresh added a commit that referenced this issue Feb 13, 2017
[release/3.2] Issue #1814 Remove findbugs warning
albinsuresh added a commit that referenced this issue Feb 13, 2017
[release/3.1] Issue #1814 Remove findbugs warning
albinsuresh added a commit that referenced this issue Feb 15, 2017
Fix #1814 Passive sync state repository data
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants