Description:
Processing for the specified MIB request was unable to locate the necessary SNMP table vector class needed to correctly return the requested attribute values.
Cause:
This is an internal error that could be the result of an invalid MIB entry or missing WebLogic class information.
Description:
Specified inclusion patterns could not be parsed
Cause:
Malformed inclusion patterns
Description:
The supported log types are defined in weblogic.diagnostics.accessor.LogTypes interface.
Cause:
This message indicates that the logical name specified to look up the DiagnosticDataAccessRuntimeMBean is not correct.
Description:
Class could not be instrumented.
Cause:
This can happen because the class may contain constructs which are unsafe to transform, eg, custom attributes.
Description:
The unRegisterInterceptionPoint method encounters some input error due to “msg“.
Cause:
Illegal usage of unRegisterInterceptionPoint API.
Description:
An exception was encountered while attempting to create a new AttributeChange JMX Monitor for the new instance.
Cause:
Please refer to exception message for more specific cause information.
Description:
Internal error. Instrumentation engine configuration is missing from the build.
Cause:
Instrumentation engine configuration is missing from the build.
Description:
A JMSException was thrown when creating the JMS objects used to send the notification to the JMS destination.
Cause:
JMS destination is not configured correctly or is not available.
Description:
Delegating monitor uses an action group which does not exist or is empty
Cause:
Incorrect or incomplete instrumentation engine configuration
Description:
The process method encounters some usage error due to “msg“.
Cause:
The required processor for the given association is not created at the time. To send message to a target that has association defined the processor specified in the association needs to be added beforehand.