This repository has been archived by the owner on Jul 19, 2021. It is now read-only.
[SUITE 2560] Prevent StackOverflowError for SecureCatalog #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch makes sure SecuredCatalogInfo objects are always created through DefaultSecureCatalogFactory.secure(Object, WrapperPolicy) and logs a warning when a secured info is being created to wrap another secured info, which ultimately can lead to a StackOverflowError at least in ResourcePool.getDataStore(), which serializes and deserializes the store using regular Java serialization.
Signed-off-by: Erik Merkle <[email protected]>
Signed-off-by: Erik Merkle <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.