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

[BACKPORT] Reset Cache.cacheManager to null when Cache is closed #13236

Conversation

@vbekiaris
Copy link
Contributor

@vbekiaris vbekiaris commented Jun 4, 2018

When a Cache is closed, it is no longer managed by the CacheManager,
so its CacheManager should be reset to null and getCacheManager() should
return null as per spec. When reopened by the same CacheManager or
a new CacheManager for the same [URI, ClassLoader], it becomes managed
and its CacheManager is set again.

(cherry picked from commit f9135a9)

Backport of #13228

When a Cache is closed, it is no longer managed by the CacheManager,
so its CacheManager should be reset to null and getCacheManager() should
return null as per spec. When reopened by the same CacheManager or
a new CacheManager for the same [URI, ClassLoader], it becomes managed
and its CacheManager is set again.

(cherry picked from commit f9135a9)
@vbekiaris
Copy link
Contributor Author

@vbekiaris vbekiaris commented Jun 4, 2018

run-lab-run

@vbekiaris
Copy link
Contributor Author

@vbekiaris vbekiaris commented Jun 4, 2018

PR builder failed with #13238

@vbekiaris vbekiaris requested review from Donnerbart and ahmetmircik Jun 4, 2018
@vbekiaris vbekiaris merged commit 69af0f2 into hazelcast:maintenance-3.x Jun 5, 2018
1 check passed
1 check passed
default Test PASSed.
Details
@vbekiaris vbekiaris deleted the vbekiaris:fixes/3.10.x/cachemanager-overwrite branch Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

5 participants
You can’t perform that action at this time.