Created attachment 29047 [details] Suggested solution to improve ContextConfig JavaClassCacheEntry objects are using too much memory causing eventually (all kinds of) out of memory errors during container startup. There is no need to save whole JavaClass in cache since only superclass name and interface names are needed in later processing. Suggested solution is attached.
Looks like a sensible improvement to me. Can you provide the patch in diff -u format to save me unpicking it please.
Created attachment 29051 [details] diff -u Here it is!
*** Bug 53615 has been marked as a duplicate of this bug. ***
Thanks for the patch. It has been applied to trunk and 7.0.x and will be included in 7.0.30 onwards.