Memory Leak in WebLogic At Weblogic.Rjvm.ConnectionManagerServer
(Doc ID 2227869.1)
Last updated on JULY 25, 2022
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 12c]
Information in this document applies to any platform.
On WebLogic Server 126.96.36.199.0 a memory leak is observered at weblogic.rjvm.ConnectionManagerServer
Below behavior is noted :-
1. WebLogic JVM young generation and old generation size continues to grow, with verbosegc logs and restart the Weblogic servers is needed to clear this.
2. Analysis of HeapDump from problem server show that multiple instances of “weblogic.rjvm.ConnectionManagerServer”, loaded by “sun.misc.Launcher$AppClassLoader” occupying the max memory
1,134 instances of "weblogic.rjvm.ConnectionManagerServer", loaded by "sun.misc.Launcher$AppClassLoader @ 0x6c0007ab0" occupy 2,166,945,856 (73.96%) bytes. These instances are referenced from one instance of "weblogic.utils.collections.ConcurrentWeakHashMap$Segment", loaded by "sun.misc.Launcher$AppClassLoader @ 0x6c0007ab0"
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