Memory Leak In SSXA In Relation To Updates Of Website Sections
Last updated on SEPTEMBER 16, 2015
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. This is one issue.
The other issue is that the old tree is not remove 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms