My Oracle Support Banner

OID 11g 11.1.1.9 Error Detected in WLS Admin and Managed Server Logs: <Error> <oracle.adf.share.ADFContext> <BEA-000000> <ADF detected an ADFContext leak. (Doc ID 2123764.1)

Last updated on FEBRUARY 01, 2019

Applies to:

Oracle Internet Directory - Version 11.1.1.9.0 and later
Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

'ADFContext leak' error is detected in WebLogic (WLS) Admin and Managed Server logs:

<Mar 31, 2016 10:14:17 JST> <Warning> <oracle.adf.share.ADFContext>
<BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.>
<Mar 31, 2016 10:14:17 JST> <Warning> <oracle.adf.share.http.ServletADFContext> <BEA-000000> <Found oracle.adf.share.DefaultContext sticking to oldContext, while the current application is em>
<Mar 31, 2016 10:14:17 JST> <Warning> <org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl> <BEA-000000> <Configurator services already initialized>
<Mar 31, 2016 10:14:22 JST> <Error> <oracle.adf.share.ADFContext> <BEA-000000> <ADF detected an ADFContext leak.
Please see the documentation for more information about handling ADFContext leaks.
For more information about the leaking ADFContext please enable logging for oracle.adf.share.ADFContext at FINEST level>

 

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.