Breadcrumb(); > Message Index (by Number) (by Subsystem) > Management Subsystem Messages

Management Subsystem Messages

The Management1.0 catalog contains messages in the range BEA140000 - BEA148999. Messages in this catalog are part of the weblogic.management.internal Internationalization package and the weblogic.i18n Localization package. BEA-140000(retired) Error: InvocationTargetException occurred while getting attribute attributeName on MBean mbean. Method: getter Description An InvocationTarget Exception occurred while attempting to get attribute attributeName on MBean mbean using Method getter. The error is t. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-140001 Error: An error occurred while getting attribute attributeName on MBean mbean. Method: getter. Exception: t. Description An error occurred while attempting to get attribute attributeName on MBean mbean using Method getter. Error is t. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-140002 Error: InvocationTargetException occurred while setting attribute attributeName on MBean mbean to value value. Method: setter. Description An InvocationTarget exception occurred while attempting to set attribute attributeName on MBean mbean to value value using Method setter. Error is setter. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-140003(retired) Warning: Targets other than the server are currently not implemented: mbean BEA-140004(retired) Debug: Notification listener listener was unregistered for the MBean mbean. It became unregistered after throwing an exception handling notification notif. BEA-140005 Notice: Loading domain configuration from configuration repository at filename. Description The administration server is loading the domain configuration from the configuration repository file filename. Cause The administration server was directed to obtain its configuration information from the specified file location. Action No action required. BEA-140006(retired) Error: Internal error. Failed to create trigger for saving configuration changes: th. Description The admin server was not able to create the scheduled trigger for persisting configuration changes. This prevents any configuration changes made by way of the the programmatic API from being saved to the configuration repository. Cause This is an internal error that may be due to resource limitations. Action Refer to details of the message body. If a dynamic configuration change is required, this might require a restart of the admin server. BEA-140007(retired) Error: Internal error. Failed to fetch RepositoryMBean to save domain - th. Description Changes made to the configuration at runtime will not be saved, as an internal error was encountered while attempting to access the Repository MBean. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Refer to the provided exception for details on what caused this error. BEA-140008 Error: Internal error. Failed to save configuration changes to the configuration repository - th. Description Changes made to the configuration at runtime failed to be saved due to an error that occurred while attempting to write to the configuration repository. Cause The config.xml file is either write-protected, or the user that has started the server is not authorized to write to this file or directory. Action Ensure that the OS user who starts the server has authorization to write to the config.xml file and that the config.xml file is not write-protected. BEA-140009(retired) Info: Configuration changes for the domain have been saved to the repository. Description This message indicates that some changes to configuration were made after starting the admin server and the changes have been saved to the configuration repository. Cause This is an information-level message only. Action No action required. BEA-140010(retired) Warning: An attribute in the MBean mbeanName refers to a non-existent MBean. Description The WeblogicObjectName specified as mbeanName does not currently exist in the WebLogic Server domain, yet an existing MBean still refers to it. Cause A dynamic change to the configuration may have been unsuccessful, resulting in the removal of mbeanName. (However, not all references to mbeanName were removed.) Action It may be necessary to restart the admin server to correct this inconsistent state. BEA-140012 Warning: Creating default domain domainName with default server serverName. Description While booting the WebLogic admin server, it was determined that no existing config.xml is present. Therefore a new default domain serverName will be created with a default server domainName. Cause This is either expected behavior or the user/script has configured an invalid environment that does not allow the booting Admin Server to locate the configuration file. Action If generation of a default configuration is not the desired behavior, please confirm that the configuration file is present and that the environment is correctly configured to identify the directory in which this configuration file is located. BEA-140013 Info: messageFromFormatter Cause This is an information-level message only. Action No action required. BEA-141000(retired) Error: Error occurred while initializing module moduleURI of application application from path path: message. Description An error was encountered while initializing application application from path path. The initialization of module moduleURI failed with the following exception: message. Cause This is probably due to a misconfigured module within the application. Refer to the specific exception content for more specific information. Action Verify that the identified module moduleURI is correctly configured for application application from path path. BEA-141001(retired) Error: Error occurred while updating deployments on target target, component component, deployments: deploymnets. BEA-141002(retired) Error: Error occurred while creating application URL urlString. Cause This is usually caused by a misconfiguration on the Server of the application URLStreamHandler. BEA-141003(retired) Error: Error occurred while parsing the application XML deployment descriptor for application application, loading from path path. BEA-141004(retired) Error: IOException occurred while opening application application, loading from path path. Description An IOException has been encountered while attempting to open application application from path path. Cause Please refer to provided exception information for complete details and probable cause. Action Verify that the specified application is correctly configured and is available at the specified path. Make sure that the user who started the server has permission to access the application. BEA-141005(retired) Error: IOException occurred while preparing exploded application application for deployment from path path. BEA-141006(retired) Error: Application application was not found at path. Description The file for application application was not found at the specified path path. Cause The specified application is either misconfigured, or the file has not been correctly made available at the specified path path. Action Either correct the application configuration to identify the correct path, or make the file available at the configured location. BEA-141007(retired) Error: Error occurred while preparing application component rootPath of application application for deployment: message (local path: localPath). Description An error was encountered while attempting to archive component rootPath for application application to distribute. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141008 Error: Error occurred while preparing application component uri of application application: t ((localPath: message). Description An error was encountered on the Admin Server while attempting to process component uri of application application from Path message. The specific exception is: t Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141009 Error: Error occurred in the file distribution servlet while processing request type "request0", t1. Description The Admin Server has encountered an error in the file distribution servlet while processing request type "request0". The exception is: t1. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141010 Error: Error occurred in the file distribution servlet, and received an unacceptable request of type "request0". Description The file distribution servlet of the Admin Server was unable to handle the request of type "request0", as it is an invalid request type not currently supported. Cause An invalid request has been made to the file distribution servlet. Action This is an internal error. No action is required. BEA-141011 Error: The file distribution servlet failed to distribute security properties file, because the file was not found at the configured location: path. Description The admin server was unable to distribute the security properties file to the managed server, because the required file was not found at the configured location: path. Cause The identified file was not available to the admin server. Action Verify the configuration of this file. BEA-141012(retired) Error: An error occurred while deploying an installed application application on server server. BEA-141013(retired) Error: An occurred while deploying an application from directory file and file t. BEA-141014 Error: An error occurred while cleaning up a temporary application directory directory. Description An error was encountered on the admin server while attempting to clean up the temporary application directory directory during deployment. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon the detailed information provided in the exception. BEA-141015 Error: Unable to create a temporary application directory directory. Description An error was encountered on the admin server while attempting to create the temporary application directory directory during deployment. Cause This is an internal error. This error is encountered during development mode deployment from the applications directory, when a temporary directory cannot be created. Action If the application failed to deploy, attempt deployment again by recopying the application into the applications directory. BEA-141016(retired) Error: An error occurred while deploying a loading application application. BEA-141017(retired) Error: The application manager deployed an application name and attempted to set the default Web application on the Web server webServerName. However, the Web server webServerName was not found. BEA-141018(retired) Error: The application manager tried to deploy the application name as a default Web application but did not find the correct components (1 Web Application) in the application: components BEA-141019(retired) Error: An error occurred while trying to deploy application application on attempt count. BEA-141020(retired) Error: An occurred while creating a domain log handler: t. Description The admin server encountered an internal error while creating the Domain Log Handler, which is used for propagating the Server Log entries to the Domain-wide log. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Contact BEA support. BEA-141021 Warning: The cluster property propName was ignored, because the server is not part of a cluster. Description The specified cluster property propName is being ignored, because the configuration of this managed server does not indicate that it is a member of a cluster. Cause A non-applicable cluster property was specified at server startup. Action Modify your configuration to identify that this managed server is, in fact, a member of a cluster, or eliminate the specification of the cluster property from the start command. BEA-141022(retired) Error: Management exception: msg. Description An internal management exception was encountered while processing the configuration. Cause This is an internal error related to configuration processing. Refer to the provided exception message for details on the cause of this problem. Action Take action based upon the detailed exception information provided. BEA-141023 Error: An error occurred while setting the attribute value in MBean Proxy proxyName, method methodName with value value (unwrapped) Description An error was encountered in the MBean Proxy proxyName while attempting to set the value value on an attribute through method methodName. Cause An invalid attribute value may have been specified. Action Verify that the provided attribute value (specified either in the configuration or through a dynamic setting) is correct. BEA-141024(retired) Error: This is not an admin server. The server cannot refresh the managed server information. Description This server is NOT an admin server and does not support the capability to maintain information on all running managed servers in the administrative domain. Cause An internal request has been incorrectly made to a managed server rather than an admin server. No internal processing has been taken for this request. Action No action required. BEA-141025(retired) Error: The listen port in file filename line lineno:line was invalid. BEA-141026(retired) Error: The line lineno:line in file filename was badly formatted. The correct format is serverName;listenAddress;listenPort. BEA-141027(retired) Warning: While trying to perform managed server discovery, it was found that server serverName (running at listenAddress:listenPort) is no longer part of the active configuration. BEA-141028 Warning: Unable to locate the managed server serverName on listen address listenAddress listen port listenPort. Description The admin server is unable to locate the managed server serverName at the listen address listenAddress listen port listenPort with exception t. Ignore this message if the managed server was shutdown intentionally. The managed server will connect to the admin server when it is re-started. Cause This is normal operation for the admin server during managed server discovery logic, if the managed server is thought to be running but was shutdown after the admin server was shutdown. Action Ignore this warning if the managed server was intentionally shutdown and is no longer running. If the managed server is still running, refer to exception details as to why the admin server was unable to reconnect. BEA-141029(retired) Warning: Unable to reconnect to the admin server running at adminUrl from this managed server, managedName. Description The managed server managedName is unable to reconnect to the admin server running at URL adminUrl due to the following exception: t. Cause Either the admin server is not currently running at the specified URL,or a network partition exists. Action Verify that the admin server is running and is not partitioned from the managed server making the request. BEA-141030(retired) Notice: Starting discovery of the managed server. This feature is on by default. You can turn this off by passing -Dweblogic.management.discover=false. Description When starting the admin server, an attempt will be made to discover all currently running managed servers for this domain. This feature is on by default. You can turn this off by passing -Dweblogic.management.discover=false. Cause This is normal processing when starting the admin server. Action You may turn this functionality off by passing -Dweblogic.management.discover=false on the start command for the admin server. BEA-141031 Info: Attempting managed server discovery for server serverName running at listenAddress:listenPort. Action No action required. BEA-141032(retired) Info: Registering managed server: serverName running at listenAddress:listenPort. Action No action required. BEA-141033(retired) Error: An error occurred while importing MBean value to server serverName. Description While attempting to make admin MBean value available to server serverName, the following exception was encountered: t. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141034(retired) Info: Java system property: key = value. Action No action required. BEA-141035(retired) Warning: No components were found in application: file. Description The application manager has identified an attempt to deploy an application file that contains no components. Cause The configured application file may not have been packaged properly, may not have the appropriate descriptor files, or may contain no components and will not be deployed. Action Make sure that the application is packaged properly with the correct descriptor files. BEA-141036(retired) Warning: An error occurred while creating domain RuntimeMBean: t. Description The admin server is unable to create the single DomainRuntimeMBean that defines the admin domain. The following exception has been raised: t. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141037(retired) Error: The file distribution servlet failed to distribute the server certificate file, because the file was not found at the configured location: path. Description The file distribution servlet failed while attempting to distribute the server certificate file from the admin server to the managed server. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141038(retired) Error: The file distribution servlet failed to distribute the server certificate chain file, because the file was not found at the configured location: path. Description The file distribution servlet failed while attempting to distribute the server certificate chain file from the admin server to the managed server. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141039(retired) Info: MBean=(mbean) Attribute=(attribute) modified from (oldValue) to (newValue). Action No action required. BEA-141040(retired) Warning: The path attribute of application is invalid. Description The path must specify a valid directory name containing the application. Cause The directories named in the path could not be created, or the application is already deployed. It is invalid to change the path of a deployed application. Action Specify a valid path for the application. BEA-141041(retired) Critical: Unable to deploy an internal management Web application - appname. Managed servers may be unable to start. Description When the server starts, it deploys some internal Web applications that are used by the management infrastructure. This indicates that there was some error in that process. This error will not allow Managed Servers to startup and/or will prevent the log viewer in the admin console from working. Cause WebLogic Server is unable to find the relevant WAR files in RootDirectory/lib. This might also be an internal failure. See the exception stack trace for any more details. Action If you are not running the server from the directory where WebLogic Server was installed, make sure that the value of the provided RootDirectory matches the directory where the WebLogic Server product was installed. Verify that a file with the application name in the log message (with a .war extension) is present in RootDirectory/lib. If not, contact BEA customer support at support@bea.com . BEA-141042(retired) Error: An error occurred while deploying an application name: t Description The admin server application poller has failed to deploy application name. The following exception was encountered while attempting this deployment: t. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Refer to the exception information and take appropriate action. BEA-141043(retired) Error: An error occurred while deploying application appname located in directory dirname: t. Description The admin server application poller has failed to deploy application appname from directory dirname. The following exception was encountered while attempting this deployment: t. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Refer to the provided exception information and take action accordingly. BEA-141044(retired) Error: Deployment of application appname failed after count attempts: t. Description The admin server application poller has failed to deploy application appname after attempting this deployment count times. The following exception was encountered while attempting this deployment: t. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Refer to the provided exception information and take action accordingly. BEA-141045(retired) Warning: Deployment of Default Web App: msg failed. BEA-141046(retired) Warning: An error has been encountered while attempting to process the deployment descriptors for deployment uri. File not found: filename. Description An error has been encountered while attempting to process the deployment descriptors for deployment uri. File filename was not found as part of descriptor processing. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141047(retired) Error: Deployment descriptor editing failed as it was unable to extract the EAR uri contents to edit the deployment descriptors from file filename. Description The deployment descriptor editing failed as it was unable to extract the EAR uri contents to edit the deployment descriptors of the application and/or modules. This is due to the fact that the temporary file filename could not be overwritten (is still open). Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141048(retired) Error: Unable to read the deployment descriptors of module uri from file filename, e. Description Exception e occurred while attempting to read the deployment descriptors for module uri from file filename. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Correct the application or the required deployment descriptors. BEA-141049(retired) Error: An error occurred while initializing module moduleURI of application application from path path: moduleURI does not exist. Other modules in this application targeted to the same server will not be deployed. Description The module identified in the application deployment descriptor does not exist. Cause The application deployment descriptor contains invalid information. Action Correct the deployment descriptor or ensure all referenced modules exist. BEA-141050(retired) Warning: Exceptions occurred while deleting application: application. Description The application files were removed from the auto-deploy directory. Exceptions were detected while cleaning up the management information associated with this application. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Refer to the provided exception information and take action accordingly. BEA-141051 Error: The operation failed with message: errorMessage. Description The WebLogic Server node manager has identified an operation failure: errorMessage. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon the details of the provided error message. BEA-141052 Info: The auto deployment poller has started. Action No action required. BEA-141053 Info: The auto deployment poller has not started for the production server. Action No action required. BEA-141054(retired) Warning: This user is not allowed to set permissions on MBean: name. Description An attempt to set multiple attributes on the MBean were rejected due to a security violation. Check the log for details. Cause This user does not have permission to set MBean attributes. Action Update the security policy for this user as necessary. BEA-141055 Warning: Failed to set attribute attrName to a value of attrValue on MBean name. The reported error was msg. Description Error msg has occurred. Cause An invalid value was specified for the attrName attribute, or the attribute is not associated with the MBean. Action Verify legal values for attribute attrName. BEA-141056(retired) Error: IOException occurred while opening application application. The path is NULL. Description An IOException occurred while opening application application, due to the path being NULL. Cause The provided application path is NULL. Action Correct the configured application application. BEA-141057(retired) Error: Unable to deploy application application as it was not loaded properly. Description Exception exception was thrown during load(). Action Please reload the application properly. BEA-141058(retired) Warning: An invalid root directory xmlValue was specified in the config.xml file. All configuration changes will be persisted to rootDir (from which the server is actually booted). BEA-141059 Info: The admin server successfully contacted the managed server, for server serverName running at listenAddress:listenPort. See the managed server log to ensure that it was able to connect back to the admin server. Action No action required. BEA-141060(retired) Info: Reconnected to the admin server running at adminUrl from the managed server - serverName. Action No action required. BEA-141061(retired) Warning: The path attribute of path is invalid for application application. Description The path must specify a valid directory name containing the application. Cause The directories named in the path could not be created, or the application is already deployed. It is invalid to change the path of a deployed application. Action Specify a valid path for the application BEA-141062 Error: This user does not have permissions to perform operation operation on MBean mbean. Method = whereOccurred, attribute = attribute Description This user does not have permissions to access the MBeans method or attribute. Cause No ACL permissions are defined for this user to complete this operation. Action The system sdministrator must add ACL permissions in order for this user to perform this operation. BEA-141063 Error: This user does not have permissions to perform operation operation on MBean mbean. Method: whereOccurred. Description A request for MBean has been issued. However, the MBean cannot be provided, since it is protected. Cause This user has no defined ACL to perform this MBean operation. Action The system administrator must define permissions in order for this user to perform this MBean operation. BEA-141064 Error: An error occurred while performing method operation on MBean mbean. Method = whereOccurred, attribute = attribute. Exception: t. Description The MBean server encountered an exception whereOccurred while calling an MBean method. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Verify that MBean mbean supports the specified operation method and that the provided parameters are valid. BEA-141065 Error: A ReflectionException has occurred: operation operation on MBean mbean. Method: whereOccurred, attribute attribute. Exception: t. Description A ReflectionException error has occurred while using the java.lang.reflect classes: operation operation on MBean mbean. Method: whereOccurred, attribute attribute. Exception: t. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141066 Error: Attribute attribute for mbean MBean does not exist. Method: whereOccurred. Exception: e Description The MBean server could not find attribute attribute for the specified MBean. Cause The MBean mbean does not currently support attribute attribute. Action Verify the MBean interface, as well as its methods and attributes. BEA-141067 Emergency: The value attributeValue specified for the attributeName attribute is not valid. MBean: mbean. Method: whereOccurred. Exception: e. Description The given value for attribute attributeName is not valid. Cause The attribute value does not meet the conditions imposed upon it. Action Modify your configuration to provide a valid attribute value for this attribute. BEA-141068(retired) Warning: Component comp could not be added to application application, as it is configured at targets that are not compatible with the application. Description This is an interoperability issue. This application configuration is already targeted to servers at a certain release level and an attempt was made to add an incompatible server. Cause The component specifies targets that are incompatible with the application. Action Add the component to a compatible version of the application. BEA-141069(retired) Error: The deployment request for application application was rejected due to incompatible targets. The application is configured for release rel. Description This is an interoperability issue. This application configuration includes target servers that are incompatible. Cause This is an invalid configuration. Action Remove any servers that are not at the same release level as what is configured for this application. BEA-141070(retired) Error: Unable to create a runtime MBean for application, application. Description A ManagementException occurred during the MBean creation. Cause This is an internal error that should not occur during normal operations. Action A stack trace was used to determine a specific error. Delete the associated ApplicationMBean. BEA-141071 Error: The file distribution servlet failed to distribute the embedded LDAP initial replica data file, because the file was not found at the configured location: path Description The embedded LDAP initial replica data file was not found at the configured location: path. Therefore, the attempt to replicate the necessary file from the admin server to the managed server has failed. Cause This is an internal error that should not occur during normal operations. Action Contact BEA support. BEA-141072(retired) Warning: AttributeChangeNotification methodName failed. The source of AttributeChangeNotification was not specified by its ObjectName. Description When AttributeChangeNotification is created, the first parameter is the source. In WebLogic Server, this source is specified by its ObjectName. Cause The AttributeChangeNotification was not created with ObjectName as its source, but it was created with another class. Action Change the AttributeChangeNotification constructor to take ObjectName as its source. BEA-141073 Info: Migration Task (taskName) - message Cause This is an information-level message. Action No action required. BEA-141074(retired) Warning: message Failed to enable/disable AttributeChangeNotification for the className MBean. The error occurred in classAndMethod. Description The admin server was unable to enable/disable AttributeChangeNotification for MBean className, since this MBean does not extend DynamicMBeanImpl. Therefore, notifications will be emitted. Cause The configuration parser will disable AttributeChangeNotifications until it finishes parsing the configuration file. Notifications will still be sent. Action Make sure that your MBean class extends DynamicMBeanImpl. BEA-141075(retired) Warning: An error occurred while retrieving the configuration file fileName from the admin server. Exception: t occurred. Description An error occurred while attempting to retrieve a configuration file fileName from the admin server. These files are retrieved so that an independent managed server can be started in the event that the admin server is unavailable at restart. Cause The admin server may be unavailable or may have encountered an internal error while processing this request. Action Verify that the admin server is running and available, and refer to the admin server log for possible additional details on the error. BEA-141076 Error: No module with URI (moduleURI) was found in (appPath). Description An error occurred while attempting to process the module with URI moduleURI within application appPath. Cause The application is potentially misconfigured relative to this module. Action Verify that the application archive and its descriptors are correctly configured. BEA-141077 Error: An error occurred during the parsing of descriptors for path. Exception e occurred. Description An error occurred while parsing the descriptor information for the application component at path during deployment. Cause Refer to the exception details for the exact cause of this parsing error. Action Take action based upon provided exception details to either correct the identified component or its descriptors. BEA-141078 Error: A descriptor initialization error occurred for module module in EAR file earPath. Creation of the temporary file e failed. Description The Deployment Descriptor Editor is creating some temporary files for parsing of the module deployment descriptor. Cause The extraction of the EAR file failed due to some IO error. See the logged exception for details. Action Make sure that the file referred to in the exception can be created, and there is no directory by the same name. BEA-141079(retired) Error: An error occurred while attempting to contact the admin server at httpurl to obtain configuration information. Will attempt to to start an independent managed server. No server log is available. Exception was: t Description An error occurred while starting the managed server and attempting to contact the admin server at URL httpurl, in order to obtain configuration information for the managed server. As a result of this failure to contact the admin server, the managed server will attempt to start independently using a local copy of its configuration. Cause Either the admin server is not currently running, or the starting managed server is unable to communicate with the admin server due to network problems. Action If it is not desirable to have the managed server running independently, either restart the admin server (if it is not running), or correct the network partition and then restart the managed server. BEA-141080(retired) Info: A request has been received to force shut down of the server. Action No action required. BEA-141081 Critical: The file distribution servlet failed to distribute the embedded LDAP initial replica data file due to the following error: msg Description The file distribution servlet has failed while attempting to distribute the LDAP initial replica data file from the admin server to the managed server. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141082(retired) Info: ServerRuntime:msge Action No action required. BEA-141083 Info: msge Action No action required. BEA-141084(retired) Error: An error occurred while setting the debug category value for categoryName. Description The debug category is not recognized. Cause An invalid debug setting was specified using the -Dweblogic.debug= specification. Action Correct the debug specification for the java weblogic.Server command. BEA-141085(retired) Error: An error occurred while setting a debug filter value for filterName. Description The debug filter value is not recognized. Cause An invalid debug filter setting was specified using the -Dweblogic.debug= specification. Action Correct the debug specification for the Java weblogic.Server command. BEA-141086 Error: An error occurred while setting a value for attr. Description Unable to change the named attribute from the command line properties. Cause The specified command line property provided an invalid value for attribute attr. Action Verify that the specified command line property provides a valid attribute value. BEA-141087 Info: Property: attr is not a recognized MBean attribute or special property used for Management. It is probably being used by subsystems and will continue to work as expected if it is a supported option. Description The named property value attr that was specified during the server start is not a known attribute. Cause An unrecognized property has been specified on the start command. Action Eliminate the invalid properties from the start command. BEA-141088 Error: Trying to initialize the admin server more than once. Description An internal error occurred while attempting to initialize the admin server singleton object more than once. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Contact BEA Support. BEA-141089 Info: Bootstrapping the server based on the WebLogic Server 6.x configuration directory structure. Description The preferred method for starting WebLogic Server is to start it from the directory that contains the domain configuration file. Cause The startup directory does not contain the configuration file, config.xml. The file was located in the config/domain directory. Action Start the server from the directory that contains the domain configuration file. BEA-141090(retired) Warning: Unable to locate config.xml at : path. Will attempt to fabricate one based on defaults. Description A default configuration will be created based on the current startup directory. Cause A configuration file, config.xml, was not found in the startup directory or the config/domain directory. Action No action is required if the exception is related to creating a new domain. Otherwise, start the server in a directory containing a valid configuration file. BEA-141091(retired) Warning: -Dweblogic.Domain= is no longer a required command line option. If you do not pass it in the domain name, it can be inferred from the configuration file: path. Description It is unnecessary to specify the domain name on the command line when starting an admin server. The domain is specified in the config file. If no configuration file exists, the domain is the name of the current directory. Cause -Dweblogic.Domain= was specified in the system properties. Action -Dweblogic.Domain= should be removed from the startup command line. BEA-141092 Error: An unexpected error occurred in method for name. Description An internal error was detected Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Contact BEA Support. BEA-141093 Error: An unexpected error occurred in postDeregister for name. The exception key is key. Description An internal error was detected while removing an MBean. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Contact BEA Support. BEA-141094(retired) Error: An unexpected error occurred while initializing the application manager. Description An internal error was detected while initializing the application manager. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Contact BEA Support. BEA-141095(retired) Error: An unexpected error occurred while running the application poller. Description An internal error was detected while running the application poller. The application poller runs in development mode to monitor new and changed applications deployed using the application directory. Cause Refer to contents of exception to find the cause of the internal poller error. Action Contact BEA Support. BEA-141096(retired) Error: A exception occurred while getting attribute attributeName on MBean objectName. Method: getter Description Unable to access an attribute for the named MBean. BEA-141097 Error: An unexpected ClassNotFoundException occurred in DynamicMBeanImpl.listToArray. Description An unexpected ClassNotFoundException occurred in the DynamicMBeanImpl processing. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Contact BEA Support. BEA-141098(retired) Error: An exception occurred while setting attribute attributeName on MBean objectName to value newValue. Method: setter Description Unable to update an attribute for the named MBean. BEA-141099(retired) Error: A migratable target error occurred for objectName. Description An error has occurred while setting the cluster for MigratableTarget objectName. Cause An invalid cluster configuration has been specified for the Migratable Target. Action Verify that the specified cluster configuration is correct. BEA-141100(retired) Warning: No DomainName was found in the configuration file. The default DomainName of name will be used. Description The configuration file did not have a Name attribute for the Domain element. Also, a DomainName was not passed on the command line using the weblogic.Domain property. Cause This is expected behavior during initial startup of the server for a new domain, where the administrator is expecting a default domain to be created as part of the admin server startup. Action No action is required. BEA-141101(retired) Warning: No DomainName was found in the configuration file defaulting to the DomainName passed in on command line, name. Description The configuration file did not have a Name attribute for the Domain element. Cause This is expected during an initial startup of the server for a new domain, where the administrator is expecting the domain to be created as part of the admin server startup, based on the weblogic.Domain property. Action No action is required. BEA-141102 Error: Subject: subject does not have access to perform roleName actions. Description The named subject attempted to perform some action within a specified role in which it is not authorized to perform. Cause Either the named subject is not allowed to perform this action and is appropriately being denied this access, or the named subject should be allowed to perform this action and the role membership of the subject is not properly configured. Action Contact the system administrator to modify role definitions. BEA-141103(retired) Notice: The managed server is shutting down, and the admin server is unavailable. message Description The managed server is unable to connect to the admin server as part of managed server shutdown processing. Cause The admin server has already been shutdown prior to the shutdown of the managed server, or it is partitioned from the managed server. Action No action is required. BEA-141107 Info: Version: version Description WebLogic Server Build Version version. Cause Normal system initialization processing. Action No action is required. BEA-141108(retired) Warning: Cannot create Abstract MBean of type a. Description An attempt has been made to create an MBean of type a. MBeans of these type are abstract and cannot be registered in the system. Cause This is likely caused by the hand editing of the config.xml, resulting in the definition of the AbstractMbean type. Action Either remove the entry from config.xml or wait until the server writes the config.xml. BEA-141109(retired) Error: Failed to update attribute for configuration MBean objectName on server server. The specified MBean does not exist in the repository. Description The admin server was unable to update attribute attribute for the configuration MBean objectName on server server. This has occurred because the specified MBean does not exist on the specified managed server, or the managed server is currently unreachable. Cause The managed server is currently unreachable, or an internal error has occurred that prevents the specified configuration MBean from being created on the managed server. Action Confirm that the managed server is reachable. BEA-141110(retired) Error: Failed to update attribute for configuration MBean objectName on server server. The value value is not valid for attribute attribute. Description The admin server was unable to update attribute attribute for the configuration MBean objectName on server server, as the specified value value was determined to be invalid. Cause The specified attribute value falls outside the determined legal value settings for this attribute. Action Verify that the specified value is appropriate for this attribute. BEA-141111(retired) Error: Failed to update attribute for the configuration MBean objectName on server server. exception Description The admin server has made an attempt to update attribute for the configuration MBean objectName on WebLogic Server server and has failed with exception: exception. Cause One of the following has occurred: the admin server was either unable to communicate with the remote managed server server; the configuration Mbean objectName was unavailable; or the request was unsuccessful. Action Verify that the managed server server is reachable. BEA-141112(retired) Error: Failed to update attribute for the configuration MBean objectName on server server. The specified attribute does not exist. Description The admin server was unable to update attribute attribute for the configuration MBean objectName on server server. The specified attribute was not found. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141113(retired) Error: The management subsystem was accessed prior to its initialization. Description There is an error in the initialization of the server that resulted in an attempt to access the management subsystem prior to its initialization. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141114(retired) Error: The URL URL specified to reconnect to the admin server was invalid. Description An internal error occurred during the process of reconnecting a managed server to its admin server. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141115(retired) Error: An invalid attempt to reconnect was initiated by the admin server currentURL. Description An internal error occurred during the process of reconnecting a managed server to its admin server. Cause This error occurs when you are actively connected to the admin server you originally booted, and that server or another server attempts to cause you to reconnect to it. Action Shutdown the admin server that is running at currentURL. BEA-141116(retired) Warning: The managed server serverName is unreachable. Description The remote managed server is unreachable either because the server was killed ungracefully or it is partitioned. Cause This error occurs when the remote server was either killed ungracefully or is unreachable (for example, it is partitioned or unresponsive). Action Either start the managed server serverName or perform a graceful shutdown. BEA-141117(retired) Warning: An invalid response code has been received from the admin server url, responseCode:message Description The server was able to make a connection to the admin server using HTTP and received a response that was not HTTP_OK. Cause The server HTTP address is not one that is recognized by the admin server. Action Check the log on the admin server to verify that it is properly functioning at the address from which the managed server is being started. BEA-141118(retired) Emergency: An error was encountered while saving the configuration for objectName in the domain domainName. Description An error occurred while generating the configuration file when persisting the MBean objectName. The original cause is defined by the nested exception. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141119(retired) Error: An internal error occurred while saving the domain domain for the MBean objectName. Description This is an unexpected internal error. This means that some part of your configuration was not able to be persisted. Cause This is an internal error that should not occur during normal operations. Action Contact BEA Support. BEA-141120 Warning: Unable to reconnect to the managed server managedServerName with the reconnect URL managedServerURL. Description The admin server is attempting to establish connectivity with the managed server after a restart or a period of being partitioned on the network. Cause This is part of normal operations. Action Check whether managed server is up and running. BEA-141121(retired) Info: The admin server is initiating a reconnect request to reconnectAdminURL. This managed server was booted with exitingAdminURL. Description This managed server was temporarily out of contact with the admin server. The admin server has come back online and is attempting to reestablish connectivity. Cause This is part of normal operations. Action No action required. BEA-141122 Error: The MBean of type className could not be found. Description This error occurs when the MBean class cannot be loaded. Cause This might occur due to an invalid request to create an MBean of an unknown type. Action Specify the correct type or set the CLASSPATH variable properly. BEA-141123(retired) Debug: Debug message: msg Description This message is emitted for debugging purposes only. Cause Some internal management error may be causing this. Action This Debug message might help with the troubleshooting of a problem. BEA-141124 Error: An invalid system property was specified while booting the server th. Description An invalid system property was specified while booting the server. Cause The server might have been started using an invalid system property. For example, starting the server using java -D weblogic.Server will throw this exception. Action Correct the invalid system property. BEA-141125 Warning: Unable to clone the boot user name and password on the remote start configuration for the newly created server. Description When a new server is created, the user name and password which the admin server was started is established as the boot name and password for remotely starting the server. This operation was unsuccessful. Cause This is most likely due to an internal error. Action Set the username and password on the RemoteStart MBean. BEA-141126 Warning: The configuration file configurationName is read only. Description Write access to file configurationName is disabled, so changes to the configuration will not be saved to disk. Cause This occurs when the write permissions on the file are not set to allow the user that booted the server to write to the config.xml file. Write access is often intentionally denied in production environments. Action In many cases, write access is intentionally denied. In such cases, this is just an informational message. If the file needs to be writable, change the permissions on the file or ask your system administrator to do so if you cannot. BEA-141127(retired) Error: The JVMRuntimeMBean was not found due to th. Description The JVMRuntimeMBean was not found. Cause This should never happen, unless you have deliberately unregistered or deleted this MBean. Action Restore the MBean or restart the server. BEA-141128(retired) Error: The JRockitRuntimeMBean was not found th. Description The JRockitRuntimeMBean was not found. Cause The JRockitRuntimeMBean is available only if you start your server with JRockit VM. Action Make sure you have started your server with JRockit VM. Also, make sure you have not overwritten the java.vendor System property. BEA-141129 Error: The managed server server was contacted but could not complete the reconnect due to an unexpected error. Description During the discovery process, the managed server was contacted and began the process of reconnecting but encountered a failure that prevented it from completely reconnecting. Cause This is likely caused by a misconfiguration of the server IP address. This is known to occur if the admin server is configured to listen on the primary interface on Windows. In that case, the address of the admin and managed servers can sometimes be resolved incorrectly and result in problems such as JNDI lookups being targeted to the wrong server. Action Change the default address on the admin server so that it is not the primary IP interface. BEA-141130(retired) Warning: The domain configuration version was not set for the domain domainName that is being started. (The current server version is version.) Description The configuration file did not have an established domain configuration version. Either this is an old config.xml that was created prior to version 7.0 or it was created by hand and the configuration version attribute was not set. Cause The configuration version is used by the server to ensure that certain behaviors remain consistent with the version of the server which the configuration file was created. This attribute was introduced in version 7.0 of WLS. If it is not present, the implication is that the configuration was created for a 6.x version of the server. Action To ensure proper functioning of the server, the ConfigurationVersion of the domain attribute should be explicitly set in the config.xml to the approriate version in the domain tag (e.g. BEA-141131(retired) Notice: A deployment is in progress to the cluster to which this server belongs. Proceeding with the start up of this server may interfere with that deployment. This could in turn lead to unexpected application behavior. To avoid this situation, this server will wait for 15 seconds to give the deployment a chance to finish. After waiting, this server will retry connecting to the admin server to continue with its start up. If the deployment is not complete by that time, further retry attempts will be made until the deployment times out in retriesLeft seconds, after which the server proceeds with the start up. Description A deployment is in progress to the cluster to which this server belongs. Proceeding with the start up of this server may interfere with that deployment. This could in turn lead to unexpected application behavior. To avoid this situation, this server will wait for 15 seconds to give the deployment a chance to finish. After waiting, this server will retry connecting to the admin server to continue with its start up. If the deployment is not complete by that time, further retry attempts will be made until the deployment times out in retriesLeft seconds, after which the server proceeds with the start up Cause A deployment is in progress to the cluster to which this server belongs. Proceeding with the start up of this server may interfere with that deployment. This could in turn lead to unexpected application behavior. To avoid this situation, this server will wait for 15 seconds to give the deployment a chance to finish. After waiting, this server will retry connecting to the admin server to continue with its start up. If the deployment is not complete by that time, further retry attempts will be made until the deployment times out in retriesLeft seconds, after which the server proceeds with the start up Action No action is necessary. After the deployment times out or completes on the admin server, the managed server will proceed with its start up. BEA-141132 Debug: Dynamic invocation while executing action action on objectName MBean instance failed. The method method with signature sig was invoked with parameters as params. Description This message is logged when a method is invoked through reflection inside DynamicMBeanImpl. Cause Execution failure, due to an exception, causes the operation to fail. Action Take appropriate action based on the error message text found in the error source. BEA-141133 Error: The Name attribute cannot be modified after the MBean objectName has been created. Description The Name attribute is read-only, because it is a key field used to identify a unique MBean instance. Cause The Name attribute is being modified by a setName operation. Action Specify the name of the MBean during creation. BEA-141134(retired) Warning: The admin server contacted the managed server to reconnect to it while it was not in a RUNNING state. Description This error is logged because the managed server has rejected the connection request. Cause The managed server locator on the admin server may have contacted the managed server while it was still booting. Action No action is required. BEA-141135(retired) Error: The managed server discovery service could not be started on the admin server. Description This error indicates that the admin server may not be able to reconnect to running managed servers. Cause This may be due to an error in parsing the running-managed-servers.xml or due to some network problem. Action Take corrective action based on the error message and restart the admin server. BEA-141136(retired) Notice: No information found about managed servers that might be running. Hence no attempt is made to discover them. Description The information about managed servers which were started previously is stored running-managed-servers.xml in the domain directory. This message indicates that this file was not found. Cause The running-managed-servers.xml does not exist because this may be a single server domain or no managed server might have been started yet. There is also a possibility that the user would have deleted this file. Action No action is required. BEA-141137(retired) Error: Managed Server was attempting to boot in Managed Server Independence mode, but was unable to complete the boot process as the Managed Server was unable to locate the cached configuration file: file Description The managed server was unable to boot in Managed Server Independence mode due to the failure to locate the cached configuration file file which must be available in order for the Managed Server to boot independently. Cause The required configuration file file is not available to the Managed Server at boot time. Action If support for Managed Server Independence is required, verify that the Server is properly configured to replicate the configuration information. BEA-141138(retired) Warning: Managed Server serverName is disconnected from the admin server. This may be either due to a managed server getting temporarily partitioned or the managed server process exiting. Description The managed server may not be reachable from the admin server anymore. Cause The managed server may have been shutdown or network partitioned. Action Rectify the network problems if there is server is getting partitioned. BEA-141139 Critical: Could not decrypt the attributeName attribute value of attributeValue from config.xml for domain domainName. If you have copied an encrypted attribute from a config.xml from another domain into the config.xml for domain domainName, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change the EmbeddedLDAP and SecurityConfiguration Credentials to "", change all other encrypted attributes to their cleartext values, then reboot the server. New credentials will be generated and all encryptable attributes will be re-encrypted. The decryption failed with the exception exceptionText. Description Decryption failed with the exception exceptionText. Cause Invalid encrypted value found in config.xml. Action If you have copied an encrypted attribute from a config.xml from another domain into the config.xml for domain domainName, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change the EmbeddedLDAP and SecurityConfiguration Credentials to "", change all other encrypted attributes to their cleartext values, then reboot the server. New credentials will be generated and all encryptable attributes will be re-encrypted. BEA-141140(retired) Info: The managed server is going to contact the admin server at bootStrapUrl to check if there exists a running admin server at this URL. Description The managed server makes a check to see whether admin server is running at the given URL. The check is made both during the managed server startup and reconnect. During the reconnect phase this check is also made on the old admin server URl to ascertain whether it is still not running. Cause This check is initiated by the managed server to check the existence of the admin server. Action No action is required. BEA-141141(retired) Warning: Failed to connect to an admin server running at url. The error message returned is msg. Description The managed server could not ascertain whether an admin server is running at the given URL. Cause This check to verify the existence of the admin server may fail to due to the admin server not running at the given URL, network problems or some other reasons. Action If the URL being checked is the old URL of the admin server then this message can be ignored otherwise examine the exception message to figure out what might have gone wrong during the check. BEA-141142(retired) Notice: The managed server has successfully reconnected to an admin server running at adminUrl. Description The managed server established reconnection to the admin server. Cause This is emitted during a reconnect initiated by the admin server during its restart. Action No action is required. BEA-141143(retired) Emergency: A null attribute info was found while localizing the MBean objectName. The MBI is mbi. Description The MBeanAttributeInfo array for the MBeanInfo contains a null element. Cause The MBeanInfo could not be loaded properly, because it may be corrupted. Action Reboot the admin and the managed server and see if the problem goes away, if it persists report problem. BEA-141144(retired) Error: An error was encountered while replicating the fileName to server serverName. Reason: msg. Description This error occurs when the Admin server is replicating MSI related files to a managed server. Cause The exception stack trace and message will explain the detailed cause for this error. Action Take corrective action based on the exception message. BEA-141145 Error: An attempt was made to connect to the administration server without credentials. Description The WLS management infrastructure provides utilities to upload files to the administration server and to transfer system files between servers. Any such operation requires that proper credentials are supplied in the request. Cause The requirement to supply credentials on all requests was added in version 8.1 of the product. It is most likely that an old version of a utility is being used that is not properly supplying these credentials. It is also possible that this represents an attempt to compromise the server. Action Determine the source of the request. If it is a legitimate request ensure that updated software is being used which properly supplies the credentials. It is also important to restrict access to the adminstartion server. Refer to the WLS documentation to ensure that all of the proper security precautions have been taken. BEA-141146 Error: An attempt was made to connect to the administration server by the user userName and a password which does not match. Description The WLS management infrastructure provides utilities to upload files to the administration server and to transfer system files between servers. Any such operation requires that proper credentials are supplied in the request. In this case the password specified for the user userName is incorrect. Cause The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities. Action Determine the source of the request. If it is a legitimate request ensure that updated software which properly supplies the credentials is in use. It is also important to restrict access to the adminstartion server. Refer to the WLS documentation to ensure that all of the proper security precautions have been taken. BEA-141147 Error: An attempt was made to upload a file to the administration server by the unauthorized user userName Description The WLS management infrastructure provides utilities to upload files to the administration server. Any such operation requires that proper credentials are supplied in the request and that specific authorization for upload is granted to that user. The user userName is not authorized to upload files. Cause The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case the user specified is not configured with the authorization to upload files. Action To enable the user to upload files to the administration server it is necessary that the user be added to the administrator or deployer role. Alternatively it is possible to authorize a user specifically for "FileUpload". Consult the server documentation for more information on how to do this. BEA-141148 Error: An invalid attempt was made to download a resourceType resource from the administration server by the unauthorized user userName. Description The WLS management infrastructure provides utilities to transfer system files between the administration server and managed servers. Any such operation requires that proper credentials are supplied in the request and that specific authorization for file download is granted to that user. The user userName is not authorized to download resources of the type resourceType Cause The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case the credentials of the user that is being used to boot the managed are used to authorize the request. That user is not authorized to access files of the type resourceType. Action Ensure that the proper credentials are being used to initiate the connection. In most cases this involves ensuring that the credentials being used to boot the managed server are properly authorized on the administration server. BEA-141149 Error: An invalid attempt was made to connect to the administration server with a salt of salt and a signature of signature, likely due to private key mismatch. Description The WLS management infrastructure provides facilities to transfer system files between servers. Any such operation requires that proper credentials are supplied in the request. In this case the security credentials between the administration server and the managed server do not match. Cause The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities. Action Determine the source of the request and ensure that the managed server and the administration server share the same security credential. That credential is stored in the domain configuration and distributed at server startup. In the case where the managed server is booted using a configuration that is different from that of the administration server, perhaps in Managed Server Independence Mode. Refer to the WLS documentation to ensure that all of the proper security precautions have been taken. BEA-141150(retired) Error: An error occurred while preparing application component uri of application application with HTTP response responseCode: message ). Description An error was encountered on the Admin Server while attempting to process component uri of application application. The HTTP response code from the administration server was responseCode and the message was message Cause This is either because the resource it self is not available on the administration server or due a misconfiguration of security such that the managed server is not properly authorized to download application resources. Action Verify the security configuration to ensure that managed server and administration server are properly configured with the same domain wide secret. BEA-141151 Emergency: The admin server could not be reached at url. Description This error indicates a failure of the managed server to connect to the admin server during its startup. Cause The admin server is not available at the specified url or the URL is not specified in the correct format like http://myhost:7001 Action Ensure that an admin server is running at the specified host and port.\n Check the url specified and in the format is correct. The url is specified by protocol://host:port, for example http://myhost:7001 BEA-141152(retired) Error: Error creating Converter: e Description The Converter encountered an internal error and could not be created. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141153(retired) Error: Error while checking for directories input: e Description The Converter is unable to access one of the provided directories for conversion. Cause The file name referenced is either not a directory or does not exist. Action Verify that the referenced directory exists. BEA-141154(retired) Warning: No weblogic.properties to Convert in the specified root. Description The Converter is unable to locate a weblogic.properties file to convert. Cause The file is not in the directory specified. Action Verify that the directory specified contains a valid weblogic.properties file. BEA-141155(retired) Error: Error creating domain in Converter: e Description The Converter encountered an internal error creating a domain. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141156(retired) Error: Error converting server data: e Description The Converter encountered an internal error converting server data. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141157(retired) Info: Startup Scripts for the Server have been created in dir Action No action is required. BEA-141158(retired) Error: Error creating Startup Scripts for the new AdminServer: e Description The Converter encountered an internal error creating StartupScripts. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141159(retired) Info: Converting type properties Action No action is required. BEA-141160(retired) Warning: Source file source does not exist. Copy the file manually after conversion to targetDir. Description The Converter failed to copy the source file. It must be manually copied after conversion. Cause The specified source file does not exist. Action Copy the file manually after conversion. BEA-141161(retired) Info: Successfully copied source to targetDir. Action No action is required. BEA-141162(retired) Warning: Failed to copy source. Copy the file manually after conversion to targetDir. Description The Converter failed to copy the source file. It must be manually copied after conversion. Cause The specified source file does not exist. Action Copy the file manually after conversion. BEA-141163(retired) Info: item name is name. Action No action is required. BEA-141164(retired) Info: ************************************* Action No action is required. BEA-141165(retired) Warning: The server server does not belong to the cluster cluster. Description The naming scheme for servers and clusters indicates a mismatch for these instances. Cause The anticipated server name does not match the cluster naming scheme. Action Review the server and cluster names. BEA-141166(retired) Info: This server does not belong to any cluster. Action No action is required. BEA-141167(retired) Error: Error creating directory dir: e Description The Converter encountered an internal error creating a directory. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141168(retired) Warning: Unable to set the Targets for WebApp appName. Targets will be set to Admin Server by default. Error: e Description An exception occurred setting a target on the webapp. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141169(retired) Warning: Not converting weblogic.system.helpPageURL as there is a link to the HelpPageURL from the console Description The help page url is not linked in the console. Cause This is an implementation change. Action No action is required. BEA-141170(retired) Warning: File notPEMFile is not in pem format and must be converted. Description The file must be converted to .pem format using the der2pem utility. Cause Current format is not supported. Action Convert the file to .pem format using the der2pem utility. BEA-141171(retired) Warning: The Converter was unable to locate securityFile. It must be copied to targetDir manually. Description The Converter failed to copy the source file. It must be manually copied after conversion. Cause The specified file does not exist. Action Copy the file manually after conversion. BEA-141172(retired) Warning: Error reading realmType Realm properties: e Description Realm properties will not be converted. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141173(retired) Warning: realmType Realm properties not found. Description Realm properties will not be converted. Cause The properties could not be located. Action No action is required. BEA-141174(retired) Warning: This version of the LDAPRealm is deprecated. Please use LDAPRealmV2 or greater. Description Realm properties will not be converted. Cause This version of the realm is not supported. Action No action is required. BEA-141175(retired) Error: Unable to convert the property property because it has an undesired value. Description The value was parsed and cannot be converted. Cause The format of this property prohibits it from conversion. Action No action is required. BEA-141176(retired) Warning: Failed adding item to exlusive set. Description Failed to add the item because the node already exists in the set. Cause No duplicates are allowed in the set. Action No action is required. BEA-141177(retired) Warning: Error setting targets for root_WebApp: e Description An exception occurred setting a target on the root_WebApp. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141178(retired) Error: Cannot create a directory named name. A file by that name already exists. Description Failed to create a directory because a file with that name already exists. Cause A file with the given name already exists. Action Make sure the directory can be created by moving like-named files. BEA-141179(retired) Error: Failed to create web.xml due to an internal error. Description The Converter encountered an internal error creating web.xml. Cause This is most likely due to an internal error. Action Contact BEA Support. BEA-141180(retired) Info: Creating webApp for the servlets registerd in the properties file. Action No action is required. BEA-141181(retired) Error: The value value is incorrectly defined for the property property and cannot be converted. Description The value cannot be parsed. Cause The format of this property prohibits it from conversion. It is likely missing an "=" character. Action Review the defined property format. BEA-141182(retired) Warning: Failed to create file. Description The Converter failed to create the specified file. Cause This is most likely due to an internal error. Action Contact BEA Support. BEA-141183 Error: Ambiguous reference in the object referrer for the attribute attribute that resolved to resolved and also otherResolved Description The config.xml contains an ambiguous reference in the object referrer for the attribute attribute that was resolved toresolved but that can also be resolved to otherResolved Cause This is generally caused when more than one target (cluster, server, domain) has the same name. In such cases the configuration is unable to determine the intended target. Action The only course of action is to rename one of the targets such that the ambiguity can be resolved consistently. BEA-141184(retired) Warning: The managed server could not unregister from the admin server as it was not reachable. Description This happens during the shutdown of a managed server, where it first attempts to inform the admin server that it is going down. Cause This is caused due to the admin server not running or it being partitioned from the network, so that it was not reachable. Action No action is required. The managed server continues its shutdown operation. BEA-141185(retired) Error: Property weblogic.Name must be specified when starting a WebLogic Managed Server via the Administration Server. Description An attempt was made to boot a managed server via the Administration Server, but the required server name was not specified. The property weblogic.Name (or weblogic.server.name) must be specified to identify the name of the Server that is to be started. Cause This is caused due to the missing specification of the server name on the java weblogic.Server command. Action Respecify the java weblogic.Server command again, including the specification of the weblogic.Name property. BEA-141186(retired) Warning: User Guest has been disabled by default. If you would like to enable Guest, you should do it manually. Description In 5.1 Guest is enabled by default. From 6.1 and beyond, user Guest has been disabled by default. Cause This is an implementation change. Action If you would like to enable guest, you should add "weblogic.security.disableGuest=false" to your weblogic.properties file before converting. BEA-141187 Info: Java system properties are defined as follows: props BEA-141188(retired) Warning: An attempt was made to set the attribute attributeName on the mbean bean to the unresolved object name reference. Description An attempt was made to set an attribute attributeName that is a reference to an another mbean on the mbean bean. The name, reference, does not resolve to a registered object name and was thus rejected. Cause The name, reference, does not resolve to a registered object name and was thus rejected. Action Check the specified object name and ensure that it is correct. BEA-141189(retired) Warning: Non-critical internal application name was not deployed. Error: message Description This is an information level message. Cause This is an information level message. Action No action required. BEA-141190 Critical: The commit phase of the configuration update failed with an exception: Description The update of the configuration file uses a 2 phase process. The commit phase of the update failed. Cause An exception occurred during the commit of the update. Action Retry the activate. Take action based upon provided exception details. BEA-141191 Warning: The prepare phase of the configuration update failed with an exception: Description The update of the configuration file uses a 2 phase process. The prepare phase of the update failed. Cause An exception occurred during the prepare of the update. Action Ensure the update is valid. Take action based upon provided exception details, make any required changes, change the changes, and retry the activate. BEA-141192 Error: The read of the edit lock file failed with an exception: Description The edit lock information is stored in a file and read at startup. The read of the file failed and the edit lock has been canceled Cause An exception occurred during the read of the edit lock file. Action Take action based upon provided exception details. Reget the edit lock. BEA-141193 Error: The write of the edit lock file failed with an exception: Description The edit lock information is stored in a file and written when changed. The write of the file failed and the edit lock has not been saved Cause An exception occurred during the write of the edit lock file. Action Take action based upon provided exception details. Reget the edit lock. BEA-141194 Error: The registration of the configuration subsystem with the deployment subsystem failed failed with an exception: Description The configuration subsystem registers with the deployment subsystem to handle deployment of configuration files. This registration failed due to an exception. Deployment of configuration files will not be processed until the error is corrected and the server is restarted. Cause An exception occurred during the registration of the configuration subsystem. Action Take action based upon provided exception details. Restart the server. BEA-141195 Error: The addOrRemote operation is not supported in 9.0 Description The method addOrRemote is no longer supported as means for deploying and undeploying JMSDestination instance to a JMSServer. Cause This mehthod was inadvertently exposed in a prior release and the functionality that represents could not be reproduced in the 9.x implementation. Action For compatibility use the setParent method on the Queue or Topic passing in the JMSServer. THe Destination is then associated exclusively with that JMSServer. BEA-141196 Error: The managed server could not update the configuration files during the registration with the deployment service. The update failed due to an exception: Description At startup, the managed server registers with the deployment service and updates any configuration files that are not at the correct version. The update of the configuration files failed. Cause An exception occurred during the update of configuration files. Action Take action based upon provided exception details, make any required changes, and retry the managed server boot. BEA-141197 Warning: The deployment of name failed. Description A deployment has failed. The cause will be visible in a previous log message. Cause An exception occurred during a resource deployment Action Take action based upon provided exception details, make any required changes, and retry the managed server boot. BEA-141198 Warning: The undeployment of name failed. Description An undeployment has failed. The cause will be visible in a previous log message. Cause An exception occurred during a resource undeployment Action Take action based upon provided exception details, make any required changes, and retry the managed server boot. BEA-141199 Critical: In the compatibility MBeanserver, the operation operation on the MBean name modified the configuration without starting an edit session and activating the changes. Description The compatibility server should start an edit session for any operations that modify the configuration. An edit session was not started and the changes were not distributed to the servers in the domain. Cause Incorrect impact information for the MBean operation.. Action Contact BEA support as this is an internal coding error that should not occur. BEA-141200 Info: Detected a domain which was created from an earlier release of WLS. The Domain will be upgraded to the current version release. Description This message indicates that the domain upgrade process will be started which will migrate the artifacts of the older domain to the current release. Cause This is an information-level message only. Action No action required. BEA-141201 Error: Unable to modify the configuration using the compatibility MBean server as other changes are pending. Activate the pending changes before modifying the configuration with the compatibility MBean server. Description The compatibility server does not support modifying the configuration when pending changes are present. Cause Modify operation invoked when changes are pending. Action Activate the changes before using the compatibility server. BEA-141202 Warning: The addition of bean key failed during the activate phase because of exception Description During a dynamic change in which the addition of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would finish the process of addition. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141203 Warning: The addition of bean key failed during the activate phase because of exception Description During a dynamic change in which the addition of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would finish the process of addition. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141204 Warning: The addition of bean key failed during the activate phase because of exception Description During a dynamic change in which the addition of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would finish the process of addition. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141205 Warning: The removal of bean key failed during the activate phase because of exception Description During a dynamic change in which the removal of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would finish the process of removal. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141206 Warning: The removal of bean key failed during the activate phase because of exception Description During a dynamic change in which the removal of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would finish the process of removal. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141207 Warning: The removal of bean key failed during the activate phase because of exception Description During a dynamic change in which the removal of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would finish the process of removal. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141208 Warning: The modification of property key failed during the activate phase because of exception Description During a dynamic change of property key an error was encountered. This occurred while trying to invoke the setter of the property. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141209 Warning: The modification of property key failed during the activate phase because of exception Description During a dynamic change of property key an error was encountered. This occurred while trying to invoke the setter of the property. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141210 Warning: The modification of property key failed during the activate phase because of exception Description During a dynamic change of property key an error was encountered. This occurred while trying to invoke the setter of the property. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141211 Error: An attempt to initialize property key failed because of exception Description During a dynamic change of property key an error was encountered. This occurred while trying to initialize the property. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141212 Error: An attempt to initialize property key failed because of exception Description During a dynamic change of property key an error was encountered. This occurred while trying to initialize the property. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141213 Error: An attempt to initialize property key failed because of exception Description During a dynamic change of property key an error was encountered. This occurred while trying to initialize the property. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141214 Error: The add of bean key failed. The exception encountered was exception Description During a dynamic change in which the addition of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would start the process of addition. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141215 Error: The add of bean key failed. The exception encountered was exception Description During a dynamic change in which the addition of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would start the process of addition. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141216 Error: The add of bean key failed. The exception encountered was exception Description During a dynamic change in which the addition of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would start the process of addition. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141217 Error: The removal of bean key failed. The exception encountered was exception Description During a dynamic change in which the removal of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would start the process of removal. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141218 Error: The removal of bean key failed. The exception encountered was exception Description During a dynamic change in which the removal of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would start the process of removal. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141219 Error: The removal of bean key failed. The exception encountered was exception Description During a dynamic change in which the removal of the bean named key was attempted an error was encountered. This occurred while trying to invoke the method that would start the process of removal. Cause See the exception for more information on the cause of this error Action The exception may have more information about the action to take BEA-141220 Critical: A required class was not found while uprading your domain. This could be possible if you did not upgrade your security provider jars to confirm with WebLogic version 9.0. You can upgrade these providers via java weblogic.Upgrade -type securityproviders. Description The security provider jars needed to be upgraded to confirm with WebLogic 9.0 classes Cause The security provider jars are not upgraded to confirm with new WebLogic 9.0 classes Action Run the upgrade tool to upgrade the provider. BEA-141221 Error: An error occurred while performing an undo of unactivated changes in the compatibility mbean server: t Description An error occurred while making changes via the compatibility MBean server. The server attempted to undo the changes that have been made, but another error occurred during the undo operation. Cause See the exception for more information. Action Check the exception message for more detail. BEA-141222 Error: Unable to download file uri for application application: message. Description During application deployment one or all files associated with the application were not accessible. Cause This is either because the resource it self is not available on the administration server or due a misconfiguration of security such that the managed server is not properly authorized to download application resources. Action Ensure the files are available and verify security configuration to ensure that managed server and administration server are properly configured with the same domain wide secret. BEA-141223 Info: The server name name specified with -Dweblogic.Name does not exist. The configuration includes the following servers serverList. Description The server name specified on the command line does not exist in the configuration. Cause The -Dweblogic.Name command line property specifies a server that does not exist in the configuration. Action Check the configuration for the list of configured servers. BEA-141224 Warning: Admin Server is not reachable. Description Admin Server is not reachable. It might be down or not responding. Cause This could be network issue. Action Check the status of Admin Server. BEA-141225 Error: The delete of pending directory file filename failed. Description During an activate or undo, the pending directory is deleted. The file could not be deleted. Cause An error occurred while deleting the file. Action Ensure that no processes have the file open for write. BEA-141226 Warning: An invalid deployment service prepare callback with id identifier was received. Description When the prepare is complete, the deployment service calls the configuration system to allow the configuration system to cleanup the pending directory. The identifier of the deployment request was not valid. Cause This indicates an internal error. Action Contact BEA support. BEA-141227 Info: Making a backup copy of the configuration at path. Description The admin server makes backup copies of the configuration file at critical points. This message indicates that the server is about to make such a backup. Cause This happens during certaing server lifecycle transitions and during configuration change. Action No action required. BEA-141228 Error: An attempt to backup the configuration to path failed with t. Description The admin server makes backup copies of the configuration file at critical points. This message indicates that a backup attempt failed. Cause See the message text for the exception message. Action Check the exception information included in the message text. BEA-141229 Notice: The upgrade process has been cancelled by the user. The server process will not be started. Description The user did not upgrade the older domain. Cause The server startup cannot proceed without upgrading the domain. Action Please upgrade the domain and then start the server. BEA-141230 Warning: Could Not locate descriptor file for System Resource : name. Description Could Not locate descriptor file for System Resource : name. File might have been deleted Cause descriptor file Could not be located in the path specified. Action Ensure that descriptor file is in the appropriate location. BEA-141231 Warning: Could Not register JSR object : t. Description Could Not register JSR object : t. Cause any Action Please look at the stacktrace and take appropriate action BEA-141232 Error: Could not decrypt the attributeName attribute value of attributeValue from the file filename. The edit session has been canceled. The decryption failed with the exception exceptionText. Description Decryption failed with the exception exceptionText. Cause Invalid encrypted value found in the edit lock file. Action Start a new edit session. BEA-141233 Error: Could not decrypt the edit lock file filename. The edit session has been canceled. The decryption failed with the exception exceptionText. Description Decryption failed with the exception exceptionText. Cause Exception occurred when decrypting the edit lock file. Action Start a new edit session. BEA-141234 Warning: A rollback of a dynamic change failed. The message for the failure is "msg". The cause of the exception is "cause". Description A rollback of a dynamic change occurred, but at least one item in the list of items to be rolled back failed. Cause See the cause field of the error message. Action Look at the possible causes of this error. The cause may give some indication of the possible actions to take. BEA-141235(retired) Info: command was issued remotely from hostAddress Description Log the host address of the machine that issued the SLC operation Cause Log the host address of the machine that issued the SLC operation Action No action needed BEA-141236(retired) Error: The delete of configuration file filename failed. Description During an activate, the configuration file could not be deleted. The file was marked to be deleted on server exit, but this may also fail. Cause An error occurred while deleting the file. Action Ensure that no processes have the file open for write. Ensure that the permissions on the directory allow for delete of this file. BEA-141237 Warning: Extraneous text found in config.xml: txt Description The config.xml file contains content text. The text will be ignored. Cause This is generally caused by mistakes in hand edited config.xml files. The config.xml is a valid XML document, however, the extraneous text is not related to any MBean attributes. Action Review the config.xml file for mistakes such as extra delimeters near the text listed in the error message. BEA-141238 Warning: A non-dynamic change has been made which affects the server server. This server must be rebooted in order to consume this change. Description Certain settings in the WebLogic configuration are considered non-dynamic. This means that servers need to be rebooted in order to consume them. When a change non-dynamic setting is detected, any servers that are affected by that change will not be included in the change. These servers will be marked as needing a reboot and will not receive any further changes until the reboot has been performed. Cause This happens when one or more of the changes made to the configuration affect non-dynamic settings. When this occurs, the affected managed servers are determined and those servers are not updated when the change is activated. In order to consume the change, these servers must be rebooted. Action Reboot the named server. BEA-141239 Warning: The non-dynamic attribute attr on beanname has been changed. This may require redeploying or rebooting configured entities Description Certain settings in the WebLogic configuration are considered non-dynamic. When such a setting is changed, the thing it is configuring may need to be reloaded. If this is a deployable, then the deployable can usually be redeployed. If it is a server or domain level setting, then one or more servers may need to be rebooted. Cause This happens when one or more of the changes made to the configuration affect non-dynamic settings. Action The required action, if any, will be indicated in a later log message. BEA-141240 Error: Found version got config file. Expected version 9 or higher config file. This could happen if you attempt to boot from the config directory rather than the domain root. Description The config.xml file contained an unexpected version. In 9.x the config.xml was moved from the domain root to the config directory. WebLogic server looks at the config and location to determine whether an upgrade is needed. Cause This could happen if you attempt to boot from the config directory rather than the domain root. Otherwise, the config could be corrupted. Action Ensure the config.xml is not corrupted and you are booting from the domain root. BEA-141241 Error: Found version got config file. Expected pre-version 9 config file. This could happen if you attempt to boot from the config directory rather than the domain root. Description The config.xml file contained an unexpected version. In 9.x the config.xml was moved from the domain root to the config directory. WebLogic server looks at the config and location to determine whether an upgrade is needed. Cause This could happen if you put a 9.x config.xml in the top level rather than in the config directory. Action Ensure the config.xml is in the correct location in the domain. BEA-141242 Error: Invalid config version found at location version = got Description The config.xml file contained an unexpected version. Cause WebLogic server found a config.xml with a version that does not match any known version of the product. Action Ensure the version string in config.xml is valid. BEA-141243 Info: The property name in element type has been deprecated in version version - message Description The config.xml file contained deprecated elements. Cause The config.xml contains elements that have been deprecated. Action Replace or remove the deprecated configuration artifacts. BEA-141244 Error: Schema validation errors while parsing file - msg Description Schema validation problems were found while parsing a configuration file Cause The WebLogic configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal depending on the setting of the system property weblogic.configuration.schemaValidationEnabled. Action See error details for specifics of the validation problem. BEA-141245 Error: Schema Validation Error in file see log for details. Schema validation can be disabled by starting the server with the command line option: prop Description Schema validation problems were found while parsing config.xml Cause The WebLogic configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal depending on the setting of the system property weblogic.configuration.schemaValidationEnabled. Action See error details for specifics of the validation problem. BEA-141246 Error: The configuration directory dir does not exist. Description The directory containing the domain configuration does not exist or is not readable. Cause The server was booted from a directory that does not contain a config directory. Action Ensure the server is booted from a valid domain directory. BEA-141247 Error: The configuration directory dir does not exist and the admin server is not available. Description On managed servers, the configuration is downloaded from the admin server. If the admin server is not available, then the server attempts to boot from a local copy of the configuration. If there is no local configuration, then the managed server cannot boot. Cause The configuration directory is missing and the admin is not available to download a copy. In this case, the managed server cannot boot. Action Ensure either the server is booted from a valid domain directory or that the admin server is available BEA-141248 Error: The configuration directory path is missing the file file Description The configuration file is missing, so the server cannot boot Cause The server was booted from a directory that does not contain a valid domain configuration Action Ensure either the server is booted from a valid domain directory. BEA-141249 Error: The configuration directory path is missing the file file and the admin server is not available to download it. Description On managed servers, the configuration is downloaded from the admin server. If the admin server is not available, then the server attempts to boot from a local copy of the configuration. If there is no local configuration, then the managed server cannot boot. Cause The server was booted from a directory that does not contain a valid configuration and the admin server is unavailable to download the current configuration files. Action Ensure either the server is booted from a valid domain directory or that the admin server is available BEA-141250(retired) Error: A critical internal application name was not deployed. Error: message Description A critical internal application name was not deployed. Error: message Cause Unknown Action Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. BEA-141251 Warning: The attribute attr from the element element was introduced in version 9.0.0.0 or later and is not valid in pre-9.0 config.xml Description An attribute was found during upgrade which is not valid in the old version. Cause An attribute that was introduced in release 9.0 or later was found in the pre-9.0 config.xml. Action Verify that the upgrade process correctly handles the named elements by reviewing the upgraded configuration files. BEA-141252 Error: The domain version, domainVersion, is greater than the release version, version, of this server. Description The DomainVersion attribute of the DomainMBean must be less than or equal to the managed server version. Cause The DomainVersion in the configuration used by the admin server is not compatible with the release version of this managed server. Action Update the WebLogic Server installation for this server. BEA-141253 Warning: An error occurred while loading the configuration translator clazz : cause Description A configuration translator specified in META-INF/wls-configuration-translators could not be loaded. Cause The message includes the specific cause. Action Repair or remove the configuration translator BEA-141254 Info: Generating new domain directory in loc Description The system will generate a new domain in the location specified Cause There was no domain directory at the location specified. Either a command line option or user input specified creation of the domain so generation of the domain is commencing. Action None. The domain directory will be generated and the server will continue to boot normally. BEA-141255 Info: Domain generation completed in milliseconds milliseconds. Description A new domain has been generated Cause A new domain has been generated Action None. The server will continue to boot normally. BEA-141256 Error: A RuntimeException occurred while adding or removing a configuration element: t Description A RuntimeException occurred while adding or removing a configuration element. Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141257 Error: An exception occurred while translating a configuration file: t Description In some cases, configuration files from earlier releases are translated for use in the current release. This error indicates a failure during translation. Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141258 Error: An exception occurred while constructing an ObjectName: t Description An exception occurred while constructing an ObjectName: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141259 Error: An exception occurred while sending a Notification: t Description An exception occurred while sending a Notification: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141260 Error: An exception occurred while removing a Notification: t Description An exception occurred while removing a Notification: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141261 Error: An exception occurred while unregister a Notification: t Description An exception occurred while unregister a Notification: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141262 Error: An exception occurred while adding a Filter: t Description An exception occurred while adding a Filter: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141263 Error: An exception occurred in an MBean customizer: t Description An exception occurred in an MBean customizer: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141264 Error: An exception occurred in an MBeanProxy: t Description An exception occurred in an MBeanProxy: t Cause See exception text for details Action The message will include information on the root cause. Review this message for indication of appropriate action. BEA-141265 Error: Could not get configuration lock used to serialize access to configuration files. Description Before reading or writing files to the pending or config directories, the configuration subsystem obtains a file lock to ensure that no other thread is writing to a file at the same time as it is being read. Cause Lock could not be obtained before the specified timeout period has elasped. Action Verify the configuration files and ensure no server has hung, thereby not releasing the lock. BEA-141266 Error: Parsing Failure in fileName: cause Description The configuration file failed to parse. Cause This error occurs when the configuration file has invalid XML syntax or other errors. Action Validate the contents of the configuration file. BEA-141267 Error: Parsing Failure in fileName on line line: cause Description The configuration file failed to parse. Cause This error occurs when the configuration file has invalid XML syntax or other errors. Action Validate the contents of the configuration file. BEA-141268 Error: Parsing Failure in fileName on line line, column column: cause Description The configuration file failed to parse. Cause This error occurs when the configuration file has invalid XML syntax or other errors. Action Validate the contents of the configuration file. BEA-141269 Warning: The temporary bean tree treeType was allocated for an undo, get, or activate operation, but has not been garbage collected. Description Temporary bean trees are used during an undo, get, or activate command. They should be garbage collected before shutdown. If not, then this may indicate a problem with a subsytem keeping a reference to the temporary bean tree.. Cause Temporary bean tree has not been garbage collected. Action Repeat the specified operation and determine if memory usage in the server is increasing. BEA-141270 Warning: Could not get configuration lock used to serialize access to configuration files. Retrying for another timeout seconds. Description Before reading or writing files to the pending or config directories, the configuration subsystem obtains a file lock to ensure that no other thread is writing to a file at the same time as it is being read. If the lock can not be obtained, the configuration subsystem will loop for a certain number of retries. Cause Another server is reading or writing to the configuration files, and the lock could not be obtained before the specified timeout period has elasped. Action No action is required. If the configuration subsystem fails to get the lock and the number of retries is exhausted, a different message with error severity will be displayed. BEA-141271 Error: An IO Exception occurred while recording setAttribute attributeName on MBean mbean. Exception: th. Description An IO Exception occurred while recording setAttribute attributeName on MBean mbean. Exception: th. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details. BEA-141272 Error: An IO Exception occurred while recording invoke operationName on MBean mbean. Exception: th. Description An IO Exception occurred while recording invoke operationName on MBean mbean. Exception: th. Cause Refer to the embedded exception information for more details as to the probable cause of this error. Action Take action based upon provided exception details.