MDS running out of memory due to no tuning.
Last updated on MARCH 08, 2017
Applies to:Oracle Metadata Services - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
An ADF 184.108.40.206.0 application using customizations stored in a MDS repository (database based) holds on to the cached pages and used memory to store the customizations even after the user has already logout for several hours. Due to this the memory is filling up and eventually will cause the server to run out of memory due to this. It is expected that MDS settings in memory are released after a user has ended his session for a while.
The memory print shows a lot of entries for class 'oracle.jsp.runtimev2.JspPageInfo'. Depending on the number of customizations and the size of the JSP page the memory footprint is even larger for a customization.
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