The Management1.0 catalog contains messages in the range
BEA145000 - BEA146000. Messages in this catalog are part of the
weblogic.management.commo
Internationalization package and the weblogic.i18ntools Localization package.
|
BEA-145000
|
Info: Initialized commo for serverType server.
|
Description
| This is a log message indicating that the initialization of commo is complete. |
|
Cause
| Initialized commo for server. |
|
Action
| No action required. |
|
|
BEA-145001
|
Error: Neither the generic classloader nor the MLet classloader th were able to load interface class s.
|
Description
| This exception is logged when you try to return a commo proxy, and the classloaders cannot load the specified interface type class. |
|
Cause
| The interface class s was not loaded. This is due to the fact that neither the generic classloader nor the MLET classloader loaded the class. |
|
Action
| Load the class by copying the MJF file to the server/lib/mbeantypes directory. |
|
|
BEA-145002
|
Error: An exception occurred while initializing commo instances from persistence.
|
Description
| Initializing of commo from persistence failed due to a runtime exception. |
|
Cause
| This might occur if you have corrupted data under the userConfig directory. The SecurityMBeans in the config.xml file might also be corrupt. |
|
Action
| Check the data under the userConfig directory for commo MBeans. You can use the weblogic.management.commo.WebLogicMBeanLoader tool to introspect the commo data. If you believe security data is corrupt, check the data in config.xml. |
|
|
BEA-145003
|
Error: An exception occured while trying to sync commo MBeans from the admin server to the managed server.
|
Description
| An exception was raised while synching commo MBeans from the admin server to the managed server. |
|
Cause
| All the commo MBeans on the managed server are registered for notification on the admin server commo MBeans. An exception may have occured during this process. |
|
Action
| Restart the managed server. If the problem persists, contact BEA support. |
|
|
BEA-145004
|
Error: An exception occurred while creating MBean:
|
Description
| An unknown exception occured while creating a commo MBean. |
|
Cause
| Check the logs for the cause of this exception. |
|
Action
| Introspect the cause and take action accordingly. |
|
|
BEA-145005
|
Notice: Wildcards are not supported for getCommoMBeans.
|
Description
| Wildcards are not supported for getCommoMBeans. |
|
Cause
| This exception is raised because wildcards are not supported for getCommoMBeans. |
|
Action
| Try to assign the wildcard an ObjectName. |
|
|
BEA-145006
|
Error: Could not load the class:
|
Description
| Could not load the class. |
|
Cause
| Classloading failed due to the fact that the classloader could not find the class, or the MLET classloader could not load the class. |
|
Action
| Check the MJFs and verify that the class the server is trying to load exists. |
|
|
BEA-145007
|
Error: An exception occurred while loading resource:
|
Description
| An exception occured while loading the resource. |
|
Cause
| Could not load the resource as stream from either the system classloader or the MLET classloader. |
|
Action
| Check the MJFs (under the server/lib/mbeantypes directory) to see if the classes containing the resource stream name exist. |
|
|
BEA-145010
|
Error: More than two files exist in directory dirName. There cannot be more than two files in an instance directory.
|
Description
| More than two files exist in directory dirName. |
|
Cause
| This might occur during a network outage while commo tries to backup the configuration. |
|
Action
| The server will not boot until this this is repaired. There are two options. (1) Boot from a previous Commo configuration by first loading CommoConfig.xml.booted. (2) Delete the older version of the offending file in the userConfig directory. Option 2 preserves all previous changes, while option 1 returns to the state at the start of the previous good session. |
|
|
BEA-145009
|
Error: An exception occurred while obtaining the commo MBean type short name.
|
Description
| An exception occurred while obtaining the commo MBean type short name. |
|
Cause
| The TypeMBean might not exist. |
|
Action
| Make sure that the TypeMBean exists. |
|
|
BEA-145011
|
Error: An exception occurred while backing up the commo configuration.
|
Description
| An exception occurred while backing up the commo configuration. |
|
Cause
| The files might be read-only. Also, check the exception log. |
|
Action
| Write-enable the directory, or refer to the raised exception and take the appropriate actions. |
|
|
BEA-145012
|
Warning: Unable to write out CommoConfig.xml.booted.
|
Description
| Unable to write out CommoConfig.xml.booted. |
|
Cause
| The file may be read only. |
|
Action
| Make the file writable, or check the exception that is logged and take the appropriate action. |
|
|
BEA-145013
|
Error: An exception occurred while initializing commo.
|
Description
| An exception occurred while initializing commo. |
|
Cause
| The commo types or instances failed to be loaded. |
|
Action
| This could be a serious issue. Contact BEA support. |
|
|
BEA-145014
|
Error: An exception occurred while creating the commo TypeMBean.u
|
Description
| An exception occurred while creating the commo TypeMBean (the root of all commo types). |
|
Cause
| The commo TypeMBean has not yet been created. |
|
Action
| This might be a serious problem. Contact BEA support. |
|
|
BEA-145015
|
Error: An exception occurred while creating a delegate object.
|
Description
| An exception occurred while trying to create a delegate object for the commo MBean that you are trying to create. |
|
Cause
| You may not have specified a delegate object while creating the commo MBean. |
|
Action
| Make sure you specify a delegate object when creating the commo MBean. |
|
|
BEA-145016
|
Error: No version data files exist for the MBean in file:
|
Description
| During load a MBean is detected with no associated data files. |
|
Cause
| The MBean was deleted in the previous session of the server. |
|
Action
| None required. Cleanup is handled automatically. |
|
|
BEA-145017
|
Error: Type incompatibility - Attr: attrName Value: attrValue Class: class
|
Description
| The Commo type and attribute associated with it are incompatable. |
|
Cause
| An attempt was made to set a Commo MBean attribute with a type-incompatible value. This can only occur through programtic access from users code. |
|
Action
| Repair the code to provide a compatible value. |
|
|
BEA-145018
|
Error: Value rejected - Attr: attrName Value: attrValue
|
Description
| Value attrValue is rejected for attribute attrName. |
|
Cause
| The attribute value is incompatible. |
|
Action
| Make sure the attribute value is compatible. |
|
|
BEA-145019
|
Error: An error occurred while setting attribute:
|
Description
| An error occurred while setting the attribute. |
|
Cause
| Check the error exception. |
|
Action
| Review the raised exception and take action accordingly. |
|
|
BEA-145020
|
Emergency: An exception occurred while trying to obtain attribute: attrName
|
Description
| An exception occurred while trying to obtain attribute attrName. |
|
Cause
| Check the logs for the exception cause. |
|
Action
| Check the logs for the exception cause and take action accordingly. |
|
|
BEA-145021
|
Error: Invalid persistence specifiers exist on MBean load:
|
Description
| Invalid persistence specifiers were found while loading the commo instance. |
|
Cause
| These values might be overwritten, or an error may have occured while setting the persistence specifiers in the registration process. |
|
Action
| Set the persistence specifiers to their original values. |
|
|
BEA-145022
|
Error: Cannot read the commo MBean due to exception:
|
Description
| Cannot read the commo MBean. |
|
Cause
| The file might be corrupted. |
|
Action
| Try to restore the corrupted file, or the server will boot with a backed up copy and delete the corrupted file after the server has successfully booted. |
|
|
BEA-145023
|
Error: An exception occurred while loading a commo MBean from persistence.
|
Description
| An exception was raised while the commo MBeans were loaded from the persistence store. |
|
Cause
| Check the message log for the exception cause. |
|
Action
| Check the raised exception in the logs and take appropriate action. |
|
|
BEA-145024
|
Error: Could not write MBean: oName to file: fileName due to exception: ex
|
Description
| Could not write MBean oName to the persistence store. |
|
Cause
| Check the exception for the most appropriate cause. |
|
Action
| Take appropriate action depending on the exception that is raised. |
|
|
BEA-145025
|
Error: An exception occurred while persisting the MBean named: oName of type: type.
|
Description
| An exception occurred while persisting the MBean named: oName of type: type. |
|
Cause
| Check the logs for the cause of this exception. |
|
Action
| The directory might be read-only; make it writeable. Also check the log and take appropriate action. |
|
|
BEA-145026
|
Error: Commo type: type is not loaded. Verify that the MJFs are under server/lib/mbeantypes.
|
Description
| Commo type type could not be found. |
|
Cause
| After building the MJF, you must copy the JAR file to the server/lib/mbeantypes directory in order for the server to find and load it. |
|
Action
| Copy the missing JAR to the server/lib/mbeantypes directory. |
|
|
BEA-145027
|
Error: An error occurred while setting the converted attribute value for attribute name. Value: convValue. The value before conversion was: beforeValue.
|
Description
| An error occurred while converting the attribute name from beforeValue to convValue. |
|
Cause
| Incompatible changes are being made. |
|
Action
| Check the value that you are trying to modify and make sure it can be modified to the specified type. |
|
|
BEA-145028
|
Error: An error occurred while setting the attribute value for attribute name. Value: value. No conversion was supplied for this type.
|
Description
| The attribute name could not be set to value value. |
|
Cause
| A conversion mechanism was not supplied. |
|
Action
| Provide a conversion mechanism. |
|
|
BEA-145029
|
Error: Cannot set the initial file location due to an exception:
|
Description
| The commo could not determine the initial file location. |
|
Cause
| Check the logged exception for the cause. This error often occurs if a malformed object name is provided. |
|
Action
| Check the logs. This error often occurs if a malformed object name is provided during registration. |
|
|
BEA-145030
|
Error: The notification listener cannot be null.
|
Description
| The notification listener that you are adding cannot be null. |
|
Cause
| The notification listener is null. |
|
Action
| Provide a notification listener that is non-null. |
|
|
BEA-145031
|
Error: An exception occured while trying to add a notification listener to a RequiredModelMBean.
|
Description
| An exception occured while trying to add a notification listener. |
|
Cause
| The listener could be null. |
|
Action
| Provide a non-null listener |
|
|
BEA-145032
|
Error: The attribute cannot be null.
|
Description
| The attribute you are setting cannot be null. |
|
Cause
| The attribute is null. |
|
Action
| Provide a non-null value for the attribute. |
|
|
BEA-145033
|
Error: An exception occured while trying to set an attribute of a RequiredModelMBean.
|
Description
| An exception occured while setting an attribute. |
|
Cause
| The attribute might have been null. Check the logs for the exception cause. |
|
Action
| Make sure the attribute is non-null. |
|
|
BEA-145034
|
Error: setAttribute failed: attrName is not found
|
Description
| An exception occurred while trying to call setAttribute. The attribute information is null. |
|
Cause
| The attribute could not be found. The attribute information is null. |
|
Action
| Verify that the attribute you are trying to set exists. |
|
|
BEA-145035
|
Error: setAttribute failed: attrName is not writable.
|
Description
| setAttribute failed for attribute attrName. The attribute is not writable. |
|
Cause
| The attribute is not writable. |
|
Action
| Make sure the attribute is writable. |
|
|
BEA-145036
|
Error: Unable to resolve the attribute value. No setMethod was defined in the descriptor for the attribute.
|
Description
| No setMethod has been defined in the descriptor for the attribute. |
|
Cause
| No setMethod is defined for this attribute. |
|
Action
| Define a setMethod for this attribute. |
|
|
BEA-145037
|
Error: An exception occured while trying to set an attribute value through a RequiredModelMBean.
|
Description
| The setMethod failed since it could not be found in the attributeDescriptor. |
|
Cause
| The setMethod could not be found for this attribute. |
|
Action
| Provide a setMethod for the attribute. |
|
|
BEA-145038
|
Error: An exception occured while trying to set an attribute value:
|
Description
| An exception occured that prevented the attribute value from being set. |
|
Cause
| The MBean instance was not found. |
|
Action
| Check the logs for the exception cause and take appropriate action. |
|
|
BEA-145039
|
Error: Cannot store MBean oname. Location could not be determined.
|
Description
| An exception occured that prevented the MBean from being written to the fileStore. |
|
Cause
| The domain directory name, and the MBean name are null. |
|
Action
| This should not happen. Either you did not register the MBean properly or the fileStore is corrupted. |
|
|
BEA-145040
|
Error: An exception occurred while getting MBeanServer.
|
Description
| An exception occurred that prevented getting the MBeanServer. |
|
Cause
| Check the logs for the appropriate exception cause. |
|
Action
| Check the logs for the reason you could not get the MBeanServer. Perhaps the username/password information is incorrect. |
|
|
BEA-145041
|
Error: It is illegal to specify a queue for a locally scoped MBean.
|
Description
| You cannot specify a queue for a locally scoped MBean. |
|
Cause
| You cannot specify a queue for a locally scoped MBean. |
|
Action
| Do not specify a queue for a locally scoped MBean. |
|
|
BEA-145042
|
Error: It is illegal to specify a notificationID for a locally-scoped MBean.
|
Description
| You cannot specify a notificationID for a locally scoped MBean. |
|
Cause
| You cannot specify a notificationID for a locally scoped MBean. |
|
Action
| Do not specify a notificationID for a locally scoped MBean. |
|
|
BEA-145043
|
Error: The ObjectName specified name is not unique across the domain. Choose a unique ObjectName.
|
Description
| You cannot use an ObjectName that is already used. |
|
Cause
| The ObjectName for a commo Mbean should be unique across the domain. |
|
Action
| Choose a unique ObjectName. |
|
|
BEA-145044
|
Error: The TypeMBean type does not exist.
|
Description
| Instance not found. An exception occured while trying to create a commo MBean. |
|
Cause
| The MBean Type that you specified is not found. |
|
Action
| Check the MJFs under server/lib/mbeantypes to verify that the MBean specifies the correct Type. |
|
|
BEA-145045
|
Error: An exception occured while invoking an operation for MBeanname.
|
Description
| An exception prevented the invoke operation on the MBean. |
|
Cause
| Check the logs for the exact exception. |
|
Action
| Check the logs for the exact exception and take appropriate action. |
|
|
BEA-145046
|
Error: MBean of Type type does not exist.
|
Description
| Instance not found. An exception occured while trying to create a commo MBean. |
|
Cause
| The MBean Type that you specified is not found. |
|
Action
| Check the MJFs under server/lib/mbeantypes to verify that the MBean Type is specified. |
|
|
BEA-145047
|
Error: Access Violation: MBean oname is not scoped to the current server server.
|
Description
| An access violation was thrown while verifying that the MBean is scoped to the current server. |
|
Cause
| You are trying to invoke an operation on a commo Mbean that is not scoped to the current server from which you are invoking. |
|
Action
| Make sure that the MBean is scoped to the current server from which you are invoking. |
|
|
BEA-145048
|
Error: Could not load MJF path. Reason: th.
|
Description
| The MJF could not be loaded for the reason logged. |
|
Cause
| The MJF was not created using the WebLogicMBeanMaker. |
|
Action
| Make sure you build the MJF using weblogic.management.commo.WebLogicMBeanMaker. |
|
|
BEA-145049
|
Warning: Tried to load a security provider jar fileName that is not upgraded. This jar will not be loaded by the server. Please run the upgrade tool on these jars to comply with the server. Not doing so might leave your server in an unstable state.
|
Description
| The provider jars that are found are built with old weblogic sources. These need to be upgraded to the newer version. User has to run the upgrade tool on these jars for system integrity. |
|
Cause
| Old security jars detected. |
|
Action
| Run the upgrade tool. |
|
