WebLogic OutOfMemoryErrors, Session Leaks, and BEA-101020 Errors Due to Incorrect Request Object Cleanup

(Doc ID 1371275.1)

Last updated on JUNE 11, 2018

Applies to:

Oracle Commerce Platform - Version 9.0 and later
Information in this document applies to any platform.


When running Oracle ATG Web Commerce with the WebLogic application server a variety of intermittent problems have been seen such as memory leaks, high session counts, requests returning blank pages, HTTP 500 errors and BEA-101020 errors.

The server log may contain stacktraces similar to the following:

####<May 16, 2011 8:46:49 AM PDT> <Error> <HTTP> <host> <application>
<[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1305560809611> <BEA-101020>
<[ServletContext@1136538732[app:example module:Example path:/example spec-version:null]]
Servlet failed with Exception
at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.initSessionInfo(ServletRequestImpl.java:2509)
at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInternal(ServletRequestImpl.java:2276)
at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(ServletRequestImpl.java:2266)
at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1272)
at atg.servlet.DynamoHttpServletRequest.getSessionRequest(DynamoHttpServletRequest.java:843)
at atg.servlet.DynamoHttpServletRequest.getRequestedSessionId(DynamoHttpServletRequest.java:5022)

Viewing the /atg/dynamo/servlet/sessiontracking/GenericSessionManager component and listing the active sessions (click the View button) may show many ATG session scopes that are "expired, with active children." similar to the following screenshot: 




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