Memory Leak Due to ThreadLocal Storage of RqlQuery Objects
Last updated on DECEMBER 22, 2016
Applies to:Oracle Commerce Platform - Version 10.2 and later
Information in this document applies to any platform.
When the server is running for a long period of time, memory consumption will increase until the server will run out of memory. Analyzing heap dumps shows a large number of RqlQuery objects (the subclasses of atg.repository.rql.RqlQuery):
The references are held by threadlocal variables (and therefore the request handling threads appear to be a huge memory consumer).
Depending on how custom code is issuing these queries, the queries are cached in threadLocal variables and never released.
Customer upgraded to 10.2 or later releases. This issue was not present prior to version 10.2.
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