14 J2EE JMX-46000 to J2EE JMX-47006
- J2EE JMX-46004: The Notifications and Notification annotations cannot be used together.
-
Cause: An MBean interface was annotated with both the @Notification and @Notifications annotations.
-
Action: Use either @Notification or @Notifications to annotate the MBean interface, but not both.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46005: The Notifications and Notification annotations cannot be used on both the management and implementation classes.
-
Cause: The @Notification or @Notifications annotation was used on both the MBean interface and MBean implementation class. Only the MBean interface should be annotated with @Notification or @Notifications.
-
Action: Remove the conflicting annotation from the implementation class.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46011: The @Inject annotation can be used only on a method that exposes a single parameter whose type is the type of the resource to be injected.
-
Cause: The JMX MBean @Inject annotation was used on a method that did not have a single parameter with the proper type.
-
Action: Change the associated MBean method to have a single parameter with the proper type or replace the @Inject annotation.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46014: A notification listener for MBean "{0}" cannot be added.
-
Cause: The MBean did not declare that it sends notifications.
-
Action: Change the MBean code to declare that it sends notifications or remove the code that attempts to register a notification listener for the MBean.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46015: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on attribute "{2}" of MBean "{3}" cannot be found.
-
Cause: The resource defined by the Description annotation that was associated with an MBean attribute was missing. The generated message specified the MBean, attribute, resource key and resource bundle.
-
Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46016: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on operation "{2}" of MBean "{3}" cannot be found.
-
Cause: The resource defined by a Description annotation that was associated with an MBean operation was missing. The generated message specified the MBean, operation, resource key and resource bundle.
-
Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46017: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on parameter "{2}" of operation "{3}" of MBean "{4}" cannot be found.
-
Cause: The resource defined by a Description annotation that was associated with an MBean operation parameter was missing. The generated message specified the MBean, operation, parameter name, resource key and resource bundle.
-
Action: Ensure that the Description annotation includes the correct resourceBundleBaseName and that the default resource bundle exists.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46018: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on MBean "{2}" cannot be found.
-
Cause: The resource defined by a Description annotation that was associated with an MBean interface was missing. The generated message specified the MBean, resource key and resource bundle.
-
Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46019: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on feature "{2}" of MBean "{3}" cannot be found.
-
Cause: A resource that was defined in one of the MBean descriptors properties (descriptionResourceKey or descriptionResourceBundleBaseName) was missing. The generated message specified the MBean, resource key and resource bundle.
-
Action: Add the resource or change the MBean descriptor property.
Level: 1
Type: WARNING
Impact: Configuration
- J2EE JMX-46020: No PersistenceManager is declared for MBean "{0}".
-
Cause: The PersistenceManagers were missing.
-
Action: When PMCompositeConfigMBeanSupport is used, specify a shared PersistenceManager or specify individual PersistenceManagers for the two config files (use injection-name 'file1' and 'file2' in mbeans.xml).
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46023: A shared PersistenceManager and an individual PersistenceManager cannot both be declared for MBean "{0}".
-
Cause: Both a shared and an individual PersistenceManager were declared for the MBean.
-
Action: When PMCompositeConfigMBeanSupport is used, specify either one shared persistence manager with no injection name, or two persistence managers with injection names "file1" and "file2", in mbeans.xml.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46024: At least one configuration object used by MBean "{0}" for type "{1}" is not registered.
-
Cause: At least one of the configuration objects used by a Composite ConfigMBean was not registered.
-
Action: Register the appropriate configuration object.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46026: The configuration file with injection name "{1}" for MBean "{0}" cannot be found.
-
Cause: The configuration file is missing or the injection name is incorrect.
-
Action: Verify that the injection name and the configuration file path are properly specified.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46028: MBean "{0}" cannot be registered,
-
Cause: An MBean was already registered with the same name. It should have been removed when the application was either stopped or undeployed.
-
Action: Examine and correct the errors that resulted when the application was stopped or undeployed, and repeat the stop or undeployment operation.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46030: failure to register MBean "{0}" during application initialization.
-
Cause: Registering the MBean during application initialization caused an error.
-
Action: Use the information from the exception stack trace to determine the cause of the error.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46032: The RequiredApplicationPermission or RequiredSystemPermission annotation is incorrect.
-
Cause: The RequiredApplicationPermission or RequiredSystemPermission annotation did not specify a nonempty action array.
-
Action: Specify a nonempty action array.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46033: The Description annotation on method "{0}" of class "{1}" is incorrect.
-
Cause: The Description annotation resourceKey was null.
-
Action: Ensure that the resourceKey for the Description annotation is not null for the method cited in the error message.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46035: The Description annotations on the mutator and accessor of attribute "{0}" are in conflict.
-
Cause: Both the mutator and the accessor were annotated. Ideally, only the mutator should be annotated. The message key and the message bundle were not identical on both the mutator and the accessor, and must be if both are annotated.
-
Action: Either remove the annotation on the accessor or ensure that the message key and the message bundle are identical on both the accessor and the mutator.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46036: OpenType "{0}" cannot be converted to a Class<?> instance.
-
Cause: The OpenType was not an instance of Class or ParameterizedType or GenericArrayType, and it must be.
-
Action: Ensure that the OpenType is an instance of Class or ParameterizedType or GenericArrayType.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46211: The FederationMBeanServerImpl constructor is being called incorrectly.
-
Cause: The constructor for FederationMBeanServerImpl was called more than once, which is not allowed.
-
Action: Call the constructor for FederationMBeanServerImpl only once.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46221: JMXFrameworkStateFactory is not initialized. JMXStateFactoryImpl.init() should have been called prior to calling this method
-
Cause: JMXFrameworkStateFactory in not initialized.
-
Action: JMXStateFactoryImpl.init() should have been called prior to calling this method.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46229: Only one of two security annotations OperationRequiredGlobalSecurityRole and OperationRequiredCustomSecurityGroup can be applied to MBean operation {0}.{1}
-
Cause: Two security annotations on the MBean operation
-
Action: Apply only one or none security annotation the the MBean operation
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46231: Only one of two security annotations AttributeGetterRequiredGlobalSecurityRole and AttributeGetterRequiredCustomSecurityGroup can be applied to MBean Attribute Getter {0}.{1}
-
Cause: Two security annotations on the MBean attribute getter
-
Action: Apply only one or none security annotations to the MBean attribute getter.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46233: Only one of two security annotations AttributeSetterRequiredGlobalSecurityRole and AttributeSetterRequiredCustomSecurityGroup can be applied to MBean Attribute Setter {0}.{1}
-
Cause: Two security annotations on the MBean attribute setter
-
Action: Apply only one or none security annotations to the MBean attribute setter.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46235: Only one of two security annotations MBeanRequiredGlobalSecurityRole and MBeanRequiredCustomSecurityGroup can be applied to MBean interface {0}
-
Cause: Two security annotations on the MBean interface
-
Action: Apply only one or none security annotations to the MBean interface.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46300: Class "{0}" is not compatible with the annotation on method "{1}" of class "{2}".
-
Cause: When a MinValue, MaxValue or LegalValues annotation was used, the class that the annotation applied to did not have either a public static valueOf(String) method or a public constructor with only a String parameter.
-
Action: Change the class that the MinValue, MaxValue or LegalValues annotation applies to so that it either has a public static valueOf(String) method or a public constructor with only a String parameter.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46301: An object cannot be obtained for the minimum value for "{0}" for method "{1}" of class "{2}".
-
Cause: An instance of the class that a MinValue annotation applied to was not constructed. The associated IllegalArgumentException indicates the reason.
-
Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46302: An object cannot be obtained for the maximum value for "{0}" for method "{1}" of class "{2}".
-
Cause: An instance of the class that a MaxValue annotation applied to was not constructed. The associated IllegalArgumentException indicates the reason.
-
Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46303: An object cannot be obtained for the valid value "{0}" for method "{1}" of class "{2}".
-
Cause: An instance of the class that a LegalValues annotation applied to was not be constructed. The associated IllegalArgumentException indicates the reason.
-
Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46304: The parameters being validated for method "{0}" of class "{1}" based on annotations do not match the method parameter types.
-
Cause: A constraint declared using the MinValue, MaxValue or LegalValues annotation was being enforced, but the number of arguments passed to the method was wrong.
-
Action: Change the code that has the call to the method to have the correct number of arguments.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46305: Parameter "{0}" of method "{1}" of class "{2}" is less than the MinValue.
-
Cause: The value for an attribute or parameter that was annotated with the MinValue annotation failed the minimum value constraint test.
-
Action: Change the value so that it does not fail the minimum value constraint test or change the annotation.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46306: Parameter "{0}" of method "{1}" of class "{2}" is greater than the MaxValue.
-
Cause: The value for an attribute or parameter that was annotated with the MaxValue annotation failed the maximum value constraint test.
-
Action: Change the value so that it does not fail the maximum value constraint test or change the annotation.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46307: Parameter "{0}" of method "{1}" of class "{2}" cannot be compared to the MinValue annotation value.
-
Cause: The class to which the MinValue annotation applied did not implement the Comparable interface.
-
Action: Use a different class that implements the Comparable interface or modify the existing class so that it implements the Comparable interface.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46308: Parameter "{0}" of method "{1}" of class "{2}" cannot be compared to the MaxValue annotation value.
-
Cause: The class to which the MaxValue annotation applied did not implement the Comparable interface.
-
Action: Use a different class that implements the Comparable interface or modify the existing class so that it implements the Comparable interface.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46309: Parameter "{0}" of method "{1}" of class "{2}" does not match any value in the LegalValues annotation.
-
Cause: The value for an attribute or parameter that was annotated with the LegalValues annotation did not match any valid value.
-
Action: Change the value so that it is one of the valid values, or change the annotation.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46310: Parameter "{0}" of method "{1}" of class "{2}" violates the constraint that the LegalValues annotation cannot be used with a MinValue or MaxValue annotation.
-
Cause: The LegalValues annotation was used at the same location with either a MaxValue or MinValue annotation.
-
Action: Either use the LegalValues annotation, or use the MaxValue or MinValue annotation.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46311: The value of the MinValue annotation is greater than the value of the MaxValue annotation for parameter "{0}" of method "{1}" of class "{2}".
-
Cause: The value used for the MinValue annotation was greater than the value used for the MaxValue annotation.
-
Action: Change the annotations so that the value used for MinValue annotation is less than the value used for the MaxValue annotation.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46312: The type used for parameter "{0}" of method "{1}" of class "{2}" is improper.
-
Cause: The value passed to an attribute or method parameter that was annotated with the MinValue or MaxValue annotation was not compared with an instance of the class used for the annotation because the type of the value was incorrect.
-
Action: Use the correct value for the attribute or method call, or change the annotation type.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46313: The delegate MBeanServerConnection cannot be null.
-
Cause: A PatternBaseDelegationHandler was being constructed without the required MBeanServerConnection argument.
-
Action: Change the code to supply the required MBeanServerConnection argument.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46315: There is no registered handler to instantiate class "{0}".
-
Cause: No handler was found to instantiate the class for the object name being used.
-
Action: Register a handler that is appropriate for the object name that is used, or use a different object name.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46318: An error occurs when registering an MBean with the ObjectName "{0}" and the implementation class "{1}".
-
Cause: An error occurred when the MBean was being registered.
-
Action: See the associated Throwable exception information cited within the error message for details on the error.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46319: An error occurs when unregistering an MBean with the ObjectName "{0}" and implementation class "{1}".
-
Cause: An error occurred when the MBean was being unregistered.
-
Action: See the associated Throwable exception information cited within the error message for details on the error.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46324: The MBeanServer object parameter for the MBeanServerForwarder is null, or it is equal to the MBeanServerForwarder, or an MBeanServer object is already set.
-
Cause: The MBeanServer argument was not valid.
-
Action: Correct the MBeanServer argument.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46331: The numbers of configuration files and persistence managers for the mbean {0} in mbeans.xml do not match
-
Cause: The injectNames for configuration files and persistence managers in mbeans.xml is inconsistent.
-
Action: Update the mbeans.xml to use correct configuration files and persistence managers.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46340: EntityResolver "{0}" failed to retrieve mbeans.xml xsd "{1}"
-
Cause: Either XSD is invalid, or proper Java Security Permissions have not been granted to JMX Framework jars if Security Manager is turned on.
-
Action: Verify xsd in mbeans.xml file, and ensure proper Security Permissions are granted to JMX Framework jars if Security Manager is turned on.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46346: EntityResolver "{0}" failed to retrieve the JMX Framework configuration xsd "{1}"
-
Cause: Either XSD is invalid, or proper Java Security Permissions have not been granted to JMX Framework jars if Security Manager is turned on.
-
Action: Verify xsd in JMX Framework configuration file, and ensure proper Security Permissions are granted to JMX Framework jars if Security Manager is turned on.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46349: Missing JMX Framework configuration file
-
Cause: Cannot find the JMX Framework configuration file.
-
Action: Ensure that you either specify a valid configuration location, or that the default configuration is included in jmxspi.jar under the META-INF directory
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46352: Invalid URL for custom MBean interceptor "{0}" jar location "{1}"
-
Cause: The wrong value was specified in the JMX Framework configuration file for the MBean interceptor jar location.
-
Action: Please correct the value in the JMX Framework configuration file.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46353: Custom MBean interceptor "{0}" jar file cannot be found at the specified location "{1}"
-
Cause: Missing jar file, or incorrect location specified in the JMX Framework configuration file.
-
Action: Please correct the value in the JMX Framework configuration file, or make sure the jar file is present
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46410: When specifying multiple "{0}" elements, the injection-name attribute is required
-
Cause: Your MBean must include a name as part of the @Injection annotations to match resources defined in mbeans.xml
-
Action: Correct the @Inject annotations in your MBean to reference resources defined in your mbeans.xml
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46503: The "{0}" call to the MBean with ObjectName "{1}" is not made in the context of a JMX configuration session.
-
Cause: The call that was made needed to be made in the context of a JMX configuration session.
-
Action: Create a JMX configuration session and then make the call.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46504: A call to commit or roll back the sesssion is not made by the owner of the JMX configuration session.
-
Cause: The call was not made by the owner of the JMX configuration session.
-
Action: This call must be made by the owner of the JMX configuration session.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46505: The Config MBean implementation object "{0}" for ObjectName "{1}" does not implement MBeanServerSupport.
-
Cause: The Config MBean implementation did not implement MBeanServerSupport.
-
Action: Correct the Config MBean implementation so that it implements MBeanServerSupport.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46507: The ObjectName "{0}" is specified when adding or removing a notification listener in a JMX configuration session.
-
Cause: Specifying ObjectName when adding or removing a notification listener is not supported in a JMX configuration session.
-
Action: Add or remove the notification listener without specifying ObjectName.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46511: MBean validation error prior to committing for ObjectName"{0}": "{1}"
-
Cause: An error occurred during validation of an MBean before committing it.
-
Action: See the base exception information cited within the error message for details on the error.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46512: MBean session life-cycle callback error for ObjectName "{0}": "{1}"
-
Cause: This error occurred when the MBean session life-cycle callback was called.
-
Action: See the base exception information cited within the error message for details on the error.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46514: An MBean of type "{0}" implements Persistable directly or implements an unknown subclass of Persistable.
-
Cause: The MBean must not implement Persistable directly and must not implement an unknown subclass of Persistable.
-
Action: Remove the use of Persistable.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46602: The aggregation operation "{0}" is invalid.
-
Cause: An invalid aggregation operator was specified.
-
Action: Verify that the aggregation operator specified is among OPERATION_AVG through OPERATION_GROUPBY defined in oracle.as.jmx.framework.bulkoperations.BulkOperationsMBean.
Level: 1
Type: WARNING
Impact: Programmatic
- J2EE JMX-46604: BulkOperationsMBean NamespaceHelper instance creation error: "{0}"
-
Cause: The provided MBean server is invalid.
-
Action: Correct the MBean server that is being provided. See the base exception information cited within the error message for details on the error.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46605: Parameter count ("{0}") does not match mbean count ("{1}")
-
Cause: The number of parameter arrays passed in does not match the number of mbeans that should be invoked
-
Action: Ensure that the correct number of parameter arrays are being passed.
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46606: non-numeric attribute {0} in aggregation
-
Cause: BukpOperationMBean Aggregation operation requires all attributes to have numeric values
-
Action: Do not use attributes with non-numeric values when using the aggregation operation provided by the BulkOperationMBean
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46607: In BukpOperationMBean Aggregation operation, aggOps and aggAttrs need to be the same length
-
Cause: In BukpOperationMBean Aggregation operation, aggOps and aggAttrs need to be the same length
-
Action: Ensure that aggOps and aggAttrs are the same length
Level: 1
Type: ERROR
Impact: Programmatic
- J2EE JMX-46608: A "null" value was passed to a BulkOperationsMBean method as part of an ObjectName[] parameter. We will ignore that value, as it would cause all MBeans to be selected. If this is the intended behavior use new ObjectName("*:*") in place of null
-
Cause: This could be due to some user code logic error, and not intended.
-
Action: If this is the intended behavior use new ObjectName("*:*") in place of null
Level: 1
Type: WARNING
Impact: Programmatic
