The Configuration Management 1.0
catalog contains messages in the range
BEA150000 - BEA159999.
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.
|
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. |
|
Action
| Verify that the URL specified for the administration server is valid and that the administration server is available and listening at the specified URL. |
|
|
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
| This could be due to the admin server being currently unavailable, or due to the specified URL: url or username: usr being 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
|
Emergency: An administration server and Windows multi-homing-related configuration issue was detected (adminHost resolves to multiple IP addresses and is thus ambiguous). 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 admin 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 DNS update.) BEA recommends solution (iii).
|
Description
| The managed server has detected that the administration server identified with the provided URL is ambigious and will 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
|
Info:
|
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
|
Info:
|
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
|
Info:
|
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
|
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 either 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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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 as a managed server 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
|
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.
|
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 local address. |
|
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-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 incorrect credentials supplied that prevents 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. |
|
