ADM1601 Received a request for registration of MBean, {0}, but it is already registered in the MBeanServer.
Cause:Registration of the MBean was unsuccessful because it is already registered.
Solution:Run 'asadmin list-mbeans' to see a list of registered MBeans
ADM1603 Unable to unregister the MBean, {0}. This MBean was never registered in the MBeanServer. In general, this should not be a problem.
Cause:Unregistration of the MBean failed because it is not registered.
Solution:Run 'asadmin list-mbeans' to see a list of registered MBeans
ADM1606 Can''t handle updating an MBean element itself ({0}). The MBean is updated in terms of its xml-attributes, none of which are dynamically reconfigurable.
Cause:Can't handle updating an MBean element
Solution:Note that none of the attributes of "mbean" element except 'enabled' and 'object-name' are modifiable dynamically. Only the properties in this element that are actually the attributes of the runtime mbean are modifiable dynamically.
ADM1607 Received an MBean change event, but the MBean, {0}, is disabled. Disabled MBeans can''t have their state changed.
Cause:Disabled MBeans are not allowed to have their state changed
Solution:Try enabling the MBean
ADM1608 An MBean with name: {0} could not be loaded. Continuing to load other MBeans";
Cause:The MBeanServer refused to load the MBean
Solution:Try redeploying the MBean
ADM1618 Can''t unregister MBean: {0}
Cause:Can not unregister the MBean. This is a non-fatal error.
Solution:Try restarting the AppServer
ADM5609 Unknown server context type [{0}]. Unable to set the config context from the event multicaster.
Cause:Event subsystem does not recognize the new implementation of the server context found in runtime.