|
|
|
|---|
JBIUT0000 |
Severe |
Internal error: Null
argument received for {0}. Cause: This is an internal error where a method
received a null argument where a non-null argument was required. Action: contact Oracle
for support, and provide the diagnostic information from the server log including the stack
trace. Resource Key: NULL_ARGUMENT |
JBIUT0001 |
Severe |
Internal error: Empty list argument received for {0}. Cause: This is an
internal error where a method received an empty list argument and a non-empty list
argument was required. Action: contact Oracle for support, and provide the diagnostic information from
the server log including the stack trace. Resource Key: EMPTY_LIST_ARGUMENT |
JBIUT0010 |
Severe |
Failed to create MBean {0};
implementation class {1} is not JMX-compliant. Cause: This is an internal error that should not
normally occur. Action: contact Oracle for support, and provide the diagnostic information from the
server log including any stack trace. Resource Key: MBEAN_CREATION_NOT_JMX_COMPLIANT |
JBIUT0011 |
Warning |
Failed to register MBean {0}; an MBean
is already registered with this name. Cause: A duplicate registration request was attempted for the
MBean. Action: This should go away at the next restart of the JBI runtime.
If the problem persists, contact Oracle for support. Resource Key: MBEAN_ALREADY_REGISTERED |
JBIUT0012 |
Severe |
Failed to register MBean {0};
JMX encountered a {1} exception. The exception message is: {2} Cause: This is an
internal error that should not normally occur. Action: contact Oracle for support, and provide the
diagnostic information from the server log including any stack trace. Resource Key: MBEAN_REGISTRATION_EXCEPTION |
JBIUT0013 |
Severe |
Failed to
register MBean; implementation class {0} is not JMX-compliant. Cause: This is an
internal error that should not normally occur. Action: contact Oracle for support, and provide the
diagnostic information from the server log including any stack trace. Resource Key: MBEAN_REGISTRATION_NOT_JMX_COMPLIANT |
JBIUT0014 |
Severe |
Failed to
unregister MBean {0}; JMX encountered a {1} exception. The exception message is: {2} Cause:
This is an internal error that should not normally occur. Action: contact Oracle for support,
and provide the diagnostic information from the server log including any stack trace.
Resource Key: MBEAN_UNREGISTRATION_EXCEPTION |
JBIUT0200 |
Severe |
Failed to convert {0} to OpenType {1}. Cause: This is an internal error
that should not normally occur. Action: contact Oracle for support, and provide the diagnostic
information from the server log including any stack trace. Resource Key: CCFG_FAILED_CONVERSION_TO_OPEN_TYPE |
JBIUT0201 |
Severe |
Failed to convert {0}
to OpenType array {1}. Cause: This is an internal error that should not normally
occur. Action: contact Oracle for support, and provide the diagnostic information from the server
log including any stack trace. Resource Key: CCFG_FAILED_CONVERSION_TO_OPEN_TYPE_AR |
JBIUT0202 |
Severe |
The operation failed since the provided application configuration has
invalid properties {0}. Cause: There is extraneous data in the application configuration data. Action: Check
the application configuration data and provide only the necessary fields. Resource Key: CCFG_CD_EXTRA_PROPS |
JBIUT0203 |
Severe |
Component configuration {0}
is not defined in the configuration meta-data. Cause: The component configuration attribute is not
defined in the components deployment descriptor. Action: The component configuration attribute is missing in
the jbi.xml file. Either it has been deprecated or it was not added.
Contact Oracle support and provide details on the descriptor. Resource Key: CCFG_ATTR_DEF_MISSING_IN_XML |
JBIUT0204 |
Severe |
Application configuration attribute
{0} is not defined in the application configuration meta-data. Cause: The application configuration attribute is
not defined in the components deployment descriptor. Action: The application configuration attribute is missing
in the jbi.xml file. Either it has been deprecated or was not added.
Contact Oracle support and provide them details on the descriptor. Resource Key: CCFG_APP_CFG_ATTR_DEF_MISSING_IN_XML |
JBIUT0205 |
Severe |
Application
configuration is not defined in the component configuration meta-data. Cause: Application configuration information is missing
in the components descriptor. Action: Contact Oracle support if the component is
expected to support application configuration. Resource Key: CCFG_APP_CFG_DEF_MISSING_IN_X |
