Use JMX Connection with IIOP will Leak Many Objects of weblogic.iiop.EndPointImpl$HeartbeatKey and javax.management.remote.rmi.RMIConnectionImpl
(Doc ID 1563559.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle WebLogic Server - Version 9.0 to 126.96.36.199
Information in this document applies to any platform.
The analysis of a heap dump shows that too many heap space is consumed by weblogic.iiop.EndPointImpl. The reference graphic looks like following:
Each time when you try to get a new JMX Connection(MBeanServerConnection) via IIOP, the jmx server side will leak 1 javax.management.remote.rmi.RMIConnectionImpl and 1 weblogic.iiop.EndPointImpl$HeartbeatKey. This will happen even when you call JMXConnector.close after the JMX connection is used.
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