Oracle ADF: Log file reports ADFContext Leak

I'm facing repetitive messages like following on production application log file:

<Jul 13, 2018, 11:33:45,489 AM CEST> <Error>
<oracle.adf.share.ADFContext> <BEA-000000> <ADFContext leak detected.
oracle.adf.share.ADFContext.setAsCurrent(ADFContext.java:1717)
oracle.adf.share.ADFContext.createDefaultContext(ADFContext.java:1337)
oracle.adf.share.ADFContext.getCurrent(ADFContext.java:1311)
oracle.adf.share.ADFContext.get(ADFContext.java:1607)
oracle.adf.share.jndi.MDSBackingStore.getMDSSession(MDSBackingStore.java:421)
oracle.adf.share.jndi.MDSBackingStore.isReadOnlyMDSStore(MDSBackingStore.java:197)
oracle.adf.share.jndi.MDSBackingStore.<init>(MDSBackingStore.java:153)


It's an ADF application developed on JDeveloper 12.2.1.3.0

I've tried to search this error but all I could find was:

a bug issue (on Oracle Support, Doc ID 2321165.1) with solution saying that "these messages can normally be ignored" and that it was a BI bug problem, ADF just reporting that. (But I'm not using BI on this project)

another site saying to modify logging level from Managed Server Log Configuration on Weblogic for class "oracle.adf.share.ADFContext" from INFO to FINEST. There's also this question here on stakoverflow, but I cannot insert any comment (need 50 point reputation) and I'm not sure it's the same problem.

I'd try to modify log level, but I'm not sure of this. I can't figure out how an higher log level can solve the problem. And will this impact on performance?

Someone solved this problem before or has suggestions?

P.S.: This is my first question here. Let me know if I have to improve the question, thanks.

1 Answer
1

Two points:

1) Oracle Note 2321165.1 refers to a different stack trace showing oracle.bi classes. That is why it is said to be a BI problem. In your stack I see the ADFContext is invoked from an internal ADF class oracle.adf.share.jndi.MDSBackingStore.getMDSSession, so it is likely this can be ignored if you only see few of these messages in the log.

2) Setting a higher logging level will not solve the issue. (If any issue is solved this way, it means the code is probably wrong!) The recommended step to raise the logging level is simply to get a full stack trace that identifies where the ADF Context is instantiated and not properly released. Once you know where the problem is, you will need to take further actions. If the code is part of your application, fix your code.

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.