Using oraext:lookup-xml with File in MDS Results in Error "ADFContext leak detected"
(Doc ID 2490098.1)
Last updated on JUNE 10, 2023
Applies to:
Oracle JDeveloper - Version 12.2.1.3.0 and laterOracle Metadata Services - Version 12.2.1.3.0 and later
Information in this document applies to any platform.
Goal
Using oraext:lookup-xml with file in MDS results in error "ADFContext leak detected".
How to overcome these errors ?
Error stack
[DefaultServer] [ERROR] [] [oracle.adf.share.ADFContext] [tid: [STANDBY].ExecuteThread: '29' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: ] [partition-name: DOMAIN] [tenant-name: GLOBAL] ADFContext leak detected.[[
oracle.adf.share.ADFContext.setAsCurrent(ADFContext.java:1509)
oracle.adf.share.ADFContext.createDefaultContext(ADFContext.java:1122)
oracle.adf.share.ADFContext.getCurrent(ADFContext.java:1096)
oracle.mds.internal.net.OraMDSURLConnection.getMDSSessionInternal(OraMDSURLConnection.java:292)
Solution
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
Goal |
Solution |
References |