The Compatibility MBean Server is Enabled, but Sometimes the CompatabilityMBeanServer Is Not Initialized Properly On A Managed Server (Doc ID 1614983.1)

Last updated on JANUARY 27, 2014

Applies to:

Oracle WebLogic Server - Version 10.3 to 10.3.5
Information in this document applies to any platform.


An application runs a JMX client on a managed server that tries to look up the deprecated configuration Mbean (with DomainConfig as the root). The client uses the deprecated MBeanServer Interface to access the MBean by looking up the interface from the WebLogic Server JNDI tree. The interface is part of the JMX 1.0 API, which has been deprecated in WebLogic since WLS 9.x. Although the Compatibility MBean Server is enabled on the WebLogic Domain, and although the JMX client finds the MBean on other managed servers in the domain, the JMX client fails to find the MBean on one of the managed servers. When the problem happens, one can see the following symptoms.

  1. A Java JMX client running on the problem managed server tries to run the following JMX query, but the query returns an empty Set:


The problem happens after a domain is restarted. Once the admin server comes up, a cron job boots many managed servers simultaneously.


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