Memory Leak in SSXA in Relation to Updates of Website Sections
(Doc ID 1502365.1)
Last updated on FEBRUARY 08, 2019
Applies to:Oracle WebCenter Content - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The website has 4000+ nodes inside. The corresponding objects in memory are about 50+MB. After the update of a single node of the website structure (delete, move, change of CSP, insert) there are duplicates of the whole tree within the memory. It is obvious that a change of one node of the tree is creating the whole tree from scratch.
Old tree is not removed from memory. There are various heap dumps to find out the root cause of the problem but it seems to be a problem with the standard implementation.
After several changes there is an OutOfMemory exception and there is a need to restart WLS. Even after undeploying SSXA from WLS a lot of objects are still in memory, including the problematic SectionNodes.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document