The Configuration Management1.0 catalog contains messages in the range
BEA150000 - BEA159899. Messages in this catalog are part of the
weblogic.management.internal
Internationalization package and the weblogic.i18n Localization package.
|
BEA-150000
|
Error: An error occurred while establishing a connection back to the adminstration server msg during startup. Since bootstrap succeeded check that msg uniquely identifies the administration server.
|
Description
| An error was encountered while the managed server was attempting to establish a connection to the administration server MBeanHome at the specified URL: msg. |
|
Cause
| An improper administration server URL has been specified, or the administration server is not available at the specified URL. Commonly this is because the managed server shares an adminstration URL with the administration server. Another possibility is that the host identified by msg, or the local host, is improperly configured - for instance an /etc/hosts or DNS lookup on the hostname results in a loopback address. |
|
Action
| Verify that the URL specified for the administration server is valid, unique and that the administration server is available and listening at the specified URL. A common problem is that the administration port is enabled and both administration server and managed server are running on the same machine. In this instance a different administration port should be selected for the managed server. Another possibility is that the host identified by msg, or the local host, is improperly configured - for instance an /etc/hosts or DNS lookup on the hostname results in a loopback address. |
|
|
BEA-150001
|
Error: An error occurred while connecting to the admin server to bootstrap through URL: url, user: usr
|
Description
| An error was encountered while the managed server was attempting to connect to the admin server to obtain configuration information. |
|
Cause
| The admin server might currently be unavailable. Or the specified URL: url or username: usr might be invalid. |
|
Action
| Confirm that the designated admin server is running, and validate that the URL: url and username: usr specified are valid for this configuration. |
|
|
BEA-150002(retired)
|
Warning: An administration server multi-homing-related configuration issue was detected. managedServerName is trying to contact adminHost, but adminHost resolves to multiple IP addresses and is thus potentially ambiguous. This is usually only a problem on Windows NT and can be safely ignored on other platforms.
|
Description
| The managed server has detected that the administration server identified with the provided URL is possibly ambigious and may not be able to be resolved consistently. |
|
Cause
| The managed server has been directed to contact the administration server using a URL that resolves to multiple IP addresses. |
|
Action
| To resolve the problem, you can do one of the following: (i) point managedServerName to an admin host different from adminHost; (ii) refer to adminHost as an admin host by IP address (-Dweblogic.admin.host=a.b.c.d); or (iii) ensure that the WebLogic Server instance that is home to the administration server on adminHost binds to (listens on) a DNS address other than adminHost. (This other DNS address needs to resolve to the IP of adminHost, and requires a DNS update.) BEA recommends solution (iii). |
|
|
BEA-150003(retired)
|
Info: objectName: Dynamic configuration change of attribute attributeName from oldValue to newValue.
|
Description
| A dynamic configuration change for attribute attributeName of MBean objectName has occurred. The old value of oldValue has been replaced with the new value newValue. This change is dynamic and will be reflected on both the admin server and the currently running managed servers. |
|
Cause
| A configuration change has been initiated, either programmatically, through the WebLogic Administration Console, or through use of the weblogic.Admin command line tool. |
|
Action
| No action required. |
|
|
BEA-150004(retired)
|
Info: objectName: Non-dynamic configuration change of attribute attributeName from oldValue to newValue.
|
Description
| A non-dynamic configuration change for attribute attributeName of MBean objectName has occured. The old value of oldValue has been replaced with the new value of newValue. This change will be reflected on the admin server but will require a restart of the managed servers in order to take effect. |
|
Cause
| A configuration change has been initiated, either programmatically, through the WebLogic Administration Console, or through use of the weblogic.Admin command line tool. |
|
Action
| No action required. |
|
|
BEA-150005(retired)
|
Info: objectName: Configuration action actionName with parameters parameters and signature signature.
|
Description
| Configuration action actionName has been performed for MBean objectName. The requested invocation is with signature signature. The specified parameters are: parameters. |
|
Cause
| This configuration action has been initiated, either programmatically, through use of the WebLogic Administration Console, or through use of one of the WebLogic command line tools. |
|
Action
| No action required. |
|
|
BEA-150006(retired)
|
Error: An error occurred while backing up the booted configuration from original to backup.
|
Description
| An error has occurred while attempting to establish a backup backup of the original booted configuration file original when booting the admin server. This backup is NOT required for a successful runtime operation. |
|
Cause
| The exception might be caused by an internal server error, or as a result of directory permission or disk space problems. |
|
Action
| Verify that write permissions are enabled for the target directory location and that sufficient disk space is available. |
|
|
BEA-150007(retired)
|
Info: The booted configuration original has been backed up at backup.
|
Description
| As part of successful admin server boot processing, a back up of the booted configuration has been saved at backup. |
|
Cause
| A back up of the booted configuration was created during normal admin server boot processing. |
|
Action
| No action required. |
|
|
BEA-150008(retired)
|
Error: Cannot connect to the admin server at adminurl because the admin server and managed server are configured to listen on the same port (port).
|
|
BEA-150009
|
Emergency: Errors were detected while attempting to connect to the admin server at adminURL during initialization of the managed server ( host:port ). The reported error was: msg. This condition generally occurs when the managed and admin servers are using the same listen address and port.
|
Description
| A subsystem violation occurred that disallowed this connection. |
|
Cause
| The managed and admin servers are using the same listen address and port. |
|
Action
| Verify that the admin and managed servers are correctly configured and that the user has the appropriate permissions to boot a managed server in this domain. |
|
|
BEA-150010(retired)
|
Emergency: The admin server URL is invalid: url.
|
Description
| The provided URL is invalid. |
|
Cause
| An invalid URL was provided for the weblogic.management.server property. |
|
Action
| Specify a valid URL for the admin server for weblogic.management.server property. The URL must be of the form http://:, where is a valid host name or IP address and is a valid port number. |
|
|
BEA-150011(retired)
|
Emergency: There was an attempt to start a managed server ( mhost:mport ) using the same address as the admin server ( ahost:aport ).
|
Description
| The managed server must use a different listen address or port than the admin server. |
|
Cause
| Incorrectly configured managed server ListenAddress and/or ListenPort. |
|
Action
| Change the managed server configuration to have unique ListenAddress/ListenPort attributes. |
|
|
BEA-150012(retired)
|
Warning: The specified value of the persistence interval value is not a valid integer as specified in the system property propertyName. Reverting to the default value of default.
|
Description
| Use of the system property propertyName allows control of the frequency with which the domain configuration is persisted. The specified value of the persistence interval value is not a valid integer. Therefore, the system reverted to the default value of default. |
|
Cause
| The attribute that was set is not a valid integer. |
|
Action
| No action is currently required, as a default value is being used. You can change the system property to a valid positive integer and restart the adminstration server. |
|
|
BEA-150013(retired)
|
Emergency: Unable to locate server server in the domain domain as configured in configFile.
|
Description
| The server was unable to boot because the name supplied ( server ) for the server was not listed in the configuration file configFile associated with the domain domain. |
|
Cause
| Either the command line parameter or the configuration is incorrect. |
|
Action
| Compare the server name you supplied using -Dweblogic.Name=server with the file $configFile looking for lines of the form (). |
|
|
BEA-150014
|
Emergency: The ManagedServerIndependence feature is disabled for this server (server).
|
Description
| This server is not able to contact that admin server, and it has been configured such that it cannot be booted in ManagedServerIndependence mode. |
|
Cause
| The specified admin server is either incorrect or not reachable on the network. |
|
Action
| Make sure your admin server is running and reachable by this server, or set the ManagedServerIndependenceEnabled attribute on this server to true. |
|
|
BEA-150015(retired)
|
Info: Connecting to the administration server adminURL to retrieve the initial configuration.
|
Description
| This message is displayed when the managed server downloads its initial configuration at the time that it is started or when it reconnects as part of the managed server rediscovery process. |
|
Cause
| Results as part of normal managed server initialization. |
|
Action
| No action required. |
|
|
BEA-150016(retired)
|
Info: This server is being started as the administration server.
|
Description
| This server is being started as the administration server and will distribute and manage the configuration for the domain. |
|
Cause
| Results as part of normal administration server initialization. |
|
Action
| No action required. |
|
|
BEA-150017(retired)
|
Info: This server is being started as a dependent managed server.
|
Description
| This server is being started as a server that retrieves its configuration from an adminstration server. |
|
Cause
| Results as part of normal managed server initialization. |
|
Action
| No action required. |
|
|
BEA-150018
|
Info: This server is being started in managed server independence mode in the absence of the admin server.
|
Description
| This server is being started in managed server independence mode and will atempt to use a local copy of the configuration to boot. |
|
Cause
| The managed server was unable to communicate with the adminstration server at the provided URL, either because the specified administration server is not running or is partitioned. |
|
Action
| Restart the administration server with managed server discovery enabled so that the running managed server can synchronize its configuration with the administration server and become centrally managed. |
|
|
BEA-150019(retired)
|
Error: The address provided to get to the admin server (adminurl) resolves to a managed server local address (localhost:adminport) rather than a remote address as expected, or the local managed server port might already be in use if you have setup domain wide admin port, please check the configuration and correct the problem.
|
Description
| The managed server cannot boot due to a configuration problem that prevents it from accessing the admin server. |
|
Cause
| The managed server was given a URL to boot from that resolves to a managed server address. If the managed server is running on the same machine as the admin server, this can be caused by a failure to specify a unique admin port. |
|
Action
| Inspect the address:port provided to the managed server from which to boot. This address should be changed to reference the admin server rather than resolving to a managed server. If the managed server is running on the same machine as the admin server, you must differentiate them by providing a unique port number. |
|
|
BEA-150020
|
Error: The managed server could not reach the admin server at adminurl.
|
Description
| The managed server cannot boot due to a configuration problem that prevents it from accessing the admin server. |
|
Cause
| The managed server was given a URL to boot from where an admin server could not be contacted. |
|
Action
| Inspect the address:port provided to the managed server from which to boot. This address should be changed to point to the admin server rather than resolving locally on the managed server. |
|
|
BEA-150021
|
Error: The admin server failed to authenticate the identity of the user username starting the managed server. The reason for the error is reason.
|
Description
| The managed server cannot boot due to incorrectly provided credentials that prevent it from being authenticated by the admin server. |
|
Cause
| The username and password combination is not correct. |
|
Action
| Inspect the username and password of the user starting the managed server and supply the correct credentials. The username and password are specified on the startup with -Dweblogic.management.username and -Dweblogic.management.password command line options to the java weblogic.Server command. |
|
|
BEA-150022(retired)
|
Error: This server is not an admin server; hence it cannot honor this bootstrap request.
|
Description
| The bootstrap servlet on a managed server is being invoked. |
|
Cause
| The managed server incorrectly contacted this server to retrieve configuration information. |
|
Action
| Supply the correct admin server URL for the managed server to startup. |
|
|
BEA-150023(retired)
|
Debug: Bootstrap servlet invoked with action action from managed server serverName.
|
Description
| The action specifies the type of info requested by the managed server. |
|
|
BEA-150024
|
Error: The server name serverName is being started again as a managed server.
|
Description
| The same server cannot be started twice in the domain. |
|
Cause
| The admin server is being started as the managed server. |
|
Action
| Specify a different server name to boot. |
|
|
BEA-150025(retired)
|
Error: The managed server serverName is already running and registered in the domain.
|
Description
| The admin server has a record of this server already running. |
|
Cause
| This happens when a managed server with the same name is being started again in the domain. |
|
Action
| Specify a different managed server name to start. |
|
|
BEA-150026
|
Error: The server serverName being started is at an invalid release level version with respect to the admin server. The major and minor versions of the admin and managed servers must be the same.
|
Description
| A managed server of a different major and minor release is attempting to boot from the admin server. |
|
Cause
| A managed server of a different major and minor release is attempting to boot from the admin server. |
|
Action
| Point the managed server to an admin server at the correct release level. |
|
|
BEA-150027
|
Error: Server name serverName not found in domain domain.
|
Description
| The managed server being started is not defined in the domain. |
|
Cause
| A managed server is started with -Dweblogic.Name with a value that is not configured in the domain. |
|
Action
| Specify the correct value of the param -Dweblogic.Name. |
|
|
BEA-150028
|
Error: A security failure or an exception occurred when retrieving the bootstrap information for the managed server.
|
Description
| An error condition was raised when trying to retrieve the configuration for the managed server. |
|
Cause
| An invalid username and password might have been supplied while staring the managed server. |
|
Action
| Supply the correct credentials. Take corrective action based on the exception details. |
|
|
BEA-150029(retired)
|
Error: There was an error reading the MBean on. The value val for attribute attr could not be read successfully.
|
Description
| The attribute value specified in the config.xml could not be interpreted correctly for the specified MBean attribute. |
|
Cause
| The config.xml is not correctly formatted. |
|
Action
| Correct the attribute value in config.xml and restart the server. |
|
|
BEA-150030
|
Debug: The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverName.
|
Description
| This request is made by a booting managed server before downloading the configuration. |
|
Cause
| This happens on managed server startup. |
|
Action
| No action is required. |
|
|
BEA-150031
|
Debug: The bootstrap servlet has finished sending the configuration to serverName.
|
Description
| This request is made by a booting managed server to download the configuration. |
|
Cause
| This happens on managed server startup. |
|
Action
| No action is required. |
|
|
BEA-150032
|
Error: The managed server did not provide any version details at initial contact.
|
Description
| A managed server of a different major and minor release is attempting to boot from the admin server. |
|
Cause
| A managed server of a different major and minor release is attempting to boot from the admin server. |
|
Action
| Point the managed server to an admin server at the correct release level. |
|
|
BEA-150033(retired)
|
Warning: The managed server should not be started in development mode.
|
Description
| The managed server should not be started in development mode. |
|
Cause
| Commandline option -Dweblogic.ProductionModeEnabled was specified to the managed server startup command. |
|
Action
| Commandline option -Dweblogic.ProductionModeEnabled is applicable only to admin server; hence that option should be removed from the managed server startup command. |
|
|
BEA-150034
|
Error: An attempt was made to download the configuration for the server serverName with out the required credentials.
|
Description
| During the boot process a connection is made to the adminstration server to download the configuration of the managed server. In this case the connection was made without the approriate credentials. |
|
Cause
| This should not happen during normal operations and may represent an atempt to compromise the server. |
|
Action
| Identify the server from which the connection was made and ensure that the username and password are being properly specified. |
|
|
BEA-150035
|
Error: An attempt was made to download the configuration for the server serverName by the user userName with an invalid password.
|
Description
| During the boot process a connection is made to the adminstration server to download the configuration of the managed server. In this case the connection was made without the approriate credentials. |
|
Cause
| This should not happen during normal operations and may represent an attempt to compromise the server. |
|
Action
| Identify the server from which the connection was made and ensure that the username and password are being properly specified. |
|
|
BEA-150036
|
Error: An attempt was made to download the configuration for the server serverName by the unauthorized user userName.
|
Description
| During the boot process a connection is made to the adminstration server to download the configuration of the managed server. In this case the connection was made by an unauthorized user. |
|
Cause
| This should not happen during normal operations and may represent an atempt to compromise the server. |
|
Action
| Identify the server from which the connection was made and ensure that the username and password are being properly specified. |
|
|
BEA-150037(retired)
|
Error: Attempt to use identical objectname: objname. Previous entry will be overwritten.
|
Description
| Multiple elements (mbeans) in the configuration are using the same objectname. Only the last element is registered. |
|
Cause
| Multiple elements (mbeans) in the configuration are using the same objectname. |
|
Action
| Make sure that elements (mbeans) in the configuration have distinct objectnames. |
|
|
BEA-150038
|
Warning: Configuration file found in the parent dir parentCfg but the root directory is empty.
|
Description
| This is to bring to the users attention that a config file was found in the parent of the root dir. It is possible that the user may be starting the server from a wrong directory. |
|
Cause
| This message indicates that there is a configuration file existing in the parent of the root dir. |
|
Action
| If the root directory specified is not correct then the user can take appropriate action otherwise this message may be ignored. |
|
|
BEA-150039
|
Error: Server name could not be determined
|
Description
| The name of the current server could not be determined. |
|
Cause
| Either it is not specified or the specified name does not exist in config.xml. |
|
Action
| Specify the correct value of the param -Dweblogic.Name. |
|
|
BEA-150040
|
Warning: Unrecognized attribute: name=value
|
Description
| An unrecognized attribute was found during upgrade of the configuration. |
|
Cause
| There was an attribute in the configuration that is not recognized. This attribute will be ignored. |
|
Action
| No action necessary. The attribute will be ignored. |
|
|
BEA-150041
|
Error: The server name name is unknown to the administration server. Check if restart is required.
|
Description
| The admin server does not know about this server. |
|
Cause
| The -Dweblogic.Name command line property specifies a server that does not exist in the configuration that is active on the administration server. This can occur if the managed server was added to the configuration along with non-dynamic changes that affect the administration server. In this case, the administration server must be restarted. |
|
Action
| Check to see if the administration server is marked as needing a restart. If it is, then restart the administration server before trying to boot this managed server. Check the configuration for the list of configured servers. |
|
|
BEA-150042
|
Critical: The -Dweblogic.management.server value of cmdURL does not specify a port that has administrator privileges. Please change the startup command to specify a -Dweblogic.management.server value of adminURL. This server will remain in managed server independence mode until started with a port that has administrator privileges.
|
Description
| When starting a managed server, the -Dweblogic.management.server property determines the host and port used to communicate with the admin server. If you have configured the admin server to have a port that supports administrator privileges, then you must specify that admin port when starting the managed server. If you specify a port that does not have administrator privileges, then the managed server will not be able to communicate with the admin server and will start and remain in managed server independence mode. |
|
Cause
| The specified admin server port does not support administrator traffic required to allow the managed server to communicate with the admin server. |
|
Action
| Change the -Dweblogic.management.server property to specify a port that has administator privileges. |
|
