Use JMX Connection with IIOP will Leak Many Objects of weblogic.iiop.EndPointImpl$HeartbeatKey and javax.management.remote.rmi.RMIConnectionImpl
Last updated on NOVEMBER 05, 2016
Applies to:Oracle WebLogic Server - Version 9.0 to 184.108.40.206
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms