The Management 1.0
catalog contains messages in the range
BEA140000 - BEA149999.
Messages in this catalog are part of the
weblogic.management.internal
Internationalization package and the
weblogic.i18n
Localization package.
|
BEA-140000
|
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
|
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
|
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
|
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
|
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 serverName with default server domainName.
|
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:
|
Cause
| This is an information-level message only. |
|
Action
| No action required. |
|
|
BEA-141000
|
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
|
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. |
|
|
BEA-141005 (retired)
|
Error: IOException occurred while preparing exploded application application for deployment from path path.
|
|
BEA-141006
|
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
|
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" for application appName1.
|
Description
| The file distribution servlet of the Admin Server was unable to handle the request of type "request0" for application appName1, 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
|
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
|
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
|
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
|
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
|
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
|
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
|
Info: Java system property: key = value.
|
Action
| No action required. |
|
|
BEA-141035
|
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 contains no components and will not be deployed. |
|
Action
| Remove the configured application or modify its contents. |
|
|
BEA-141036
|
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
|
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
|
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
|
Info: MBean=(mbean) Attribute=(attribute) modified from (oldValue) to (newValue).
|
Action
| No action required. |
|
|
BEA-141040
|
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
|
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
|
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
|
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
|
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
|
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
|
Warning: 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
|
Warning: 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
|
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
|
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 application poller has started for the development server.
|
Action
| No action required. |
|
|
BEA-141053
|
Info: The application 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
|
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 sucessfully 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
|
Info: Reconnected to the admin server running at adminUrl from the managed server - serverName.
|
Action
| No action required. |
|
|
BEA-141061
|
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
|
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
|
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
|
Warning:
|
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
|
Warning: An error occured 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
|
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
|
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
|
Info: ServerRuntime:msge
|
Action
| No action required. |
|
|
BEA-141083
|
Info:
|
Action
| No action required. |
|
|
BEA-141084
|
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
|
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
|
Warning: Unrecognized property: attr.
|
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 initilize 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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
Warning: An invalid response code has been received from the admin server url, responseCode:message
|
Description
| The server was able to make a connnection 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
|
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
|
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
| No action required. |
|
|
BEA-141121
|
Info: The admin server is initiating a reconnect request to reconnectAdminURL. This managed server was booted with exitingAdminURL.
|
Description
| This managed server was temprorarily out of contact with the admin server. The admin server has come back online and is atempting 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
|
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 with 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 adminstrator to do so if you cannot. |
|
|
BEA-141127
|
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
|
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
|
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 with 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
|
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
|
Error: 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
|
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
|
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
|
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
|
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
|
Alert: Managed Server serverName got disconnected from the admin server.
|
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
|
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 startp 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
|
Warning: Failed to connect to an admin server running at bootStrapUrl.
|
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
|
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. |
|
