RAM Class Persistence: Remove dynamic Proxy classes from RCP cache #22925
+6 −0
Conversation
This file contains hidden or 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
Dynamic Proxy names are assigned in OpenJDK according to the order of the method Proxy.newProxyInstance() invoked from applications. It's problem in restore run, because the order of the method Proxy.newProxyInstance() invoked from applications may be changed on conditions or events and the class lookup by the names of $ProxyN {0...n} from RCP cache may be wrong result. The changes are proposed to remove the classes along with unsafe classes from RCP cache. Fixes: eclipse-openj9#22841 Co-authored-by: Tobi Ajila tobi_ajila@ca.ibm.com 
lzhou2025 force-pushed the castException branch from 1e92661 to eee9e5d Compare lzhou2025 changed the title Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
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.
Dynamic Proxy names are assigned in OpenJDK according to the order of the method Proxy.newProxyInstance() invoked from applications. It's problem in restore run, because the order of the method Proxy.newProxyInstance() invoked from applications may be changed on conditions or events and the class lookup by the names of $ProxyN {0...n} from RCP cache may be wrong result. The changes are proposed to remove the classes along with unsafe classes from RCP cache.
Fixes: #22841
Co-authored-by: Tobi Ajila tobi_ajila@ca.ibm.com