RESTful Management Services Leads to Memory Usage in weblogic.servlet.internal.session.MemorySessionContext
(Doc ID 2315350.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle WebLogic Server - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
Using a python script to access the RESTful management services through a common URL that follows a common format:
http(s)://[host]:[port]/management/weblogic/<version>/serverRuntime
Heap usage goes up over time, a heap dump shows the following symptoms
1)
One instance of "weblogic.servlet.internal.session.MemorySessionContext" loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0xeaaad098" occupies 112,578,776 (24.96%) bytes.
The memory is accumulated in one instance of "java.util.Hashtable$Entry[]" loaded by "<system
class loader>"
2)
One instance of "weblogic.servlet.internal.HttpServer" loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0xeaaad098" occupies 55,835,336 (12.38%) bytes.
The memory is accumulated in one instance of "weblogic.servlet.internal.HttpServer$SessionLogin" loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0xeaaad098".
3)
106,739 instances of "weblogic.security.acl.internal.AuthenticatedSubject", loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0xeaaad098" occupy 153,704,152 (34.08%) bytes.
These instances are referenced from one instance of "java.util.concurrent.ConcurrentHashMap$Node[]", loaded by "<system
class loader>"
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 |