The Deployer1.0 catalog contains messages in the range
BEA149600 - BEA149699. Messages in this catalog are part of the
weblogic.management.deploy.internal
Internationalization package and the weblogic.i18ntools Localization package.
|
BEA-149600(retired)
|
Error: The deployment framework was unable to suspend accepting requests.
|
Description
| The deployment framework failed to suspend accepting requests. |
|
Cause
| This is an internal error. |
|
Action
| Report this error to BEA support. |
|
|
BEA-149601
|
Error: The deployment framework was unable to resume accepting requests.
|
Description
| The deployment framework resume failed. |
|
Cause
| This is an internal server error. |
|
Action
| Report to error to BEA support. |
|
|
BEA-149603
|
Error: The deployment framework was unable to cleanly shutdown.
|
Description
| The deployment framework failed to shutdown cleanly. |
|
Cause
| This is an internal error. |
|
Action
| Report to this error to BEA support. |
|
|
BEA-149604(retired)
|
Error: Encountered an old/corrupt running-managed-servers.xml file. Delete the file and try again.
|
Description
| Corrupt running-managed-servers.xml file encountered. Delete this file and restart the system. |
|
Cause
| A corrupt file was encountered. |
|
Action
| Delete the running-managed-servers.xml file and restart the server. |
|
|
BEA-149605
|
Error: Failed to create App/Comp mbeans for AppDeploymentMBean name. Error - th.
|
Description
| Some error was found in the AppDeploymentMBean. |
|
Cause
| Some error was found in the AppDeploymentMBean. |
|
Action
| Reconfigure AppDeploymentMBean. |
|
|
BEA-149606
|
Error: Failed to configure deployment mbean for name.
|
Description
| Some error was found in configuring deployment mbean. |
|
Cause
| Some error was found in configuring deployment mbean. |
|
Action
| Review the application and reconfigure it. |
|
|
BEA-149607
|
Error: Failed to persist state for deployment with name name. th
|
Description
| The admin server was unable to update state information of a deployment in its persistent store. This may result in tools showing the incorrect state for this deployment. |
|
Cause
| Please see exception. |
|
Action
| Please see exception. You should undeploy and deploy after correcting the problem. |
|
|
BEA-149608
|
Error: Unknown type of deployable: 'name'
|
Description
| Unknown type of deployable: 'name' |
|
Cause
| Unknown type of deployable: 'name' |
|
Action
| See exception cause and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149609
|
Error: AppRuntimeStateRuntime only available on admin server
|
Description
| AppRuntimeStateRuntime only available on admin server |
|
Cause
| AppRuntimeStateRuntime only available on admin server |
|
Action
| Ensure the admin server is running and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149610
|
Error: There were problems creating the persistent store.
|
Description
| There were problems creating the persistent store. |
|
Cause
| The exception thrown: cause |
|
Action
| See exception cause and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149611
|
Error: There were problems reading from the persistent store.
|
Description
| There were problems reading from the persistent store. |
|
Cause
| The exception thrown: cause |
|
Action
| See exception cause and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149612
|
Error: There were problems saving to the persistent store for 'appState'.
|
Description
| There were problems saving to the persistent store for 'appState'. |
|
Cause
| cause |
|
Action
| See exception cause and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149613
|
Error: There were problems deleting from the persistent store for 'appState'.
|
Description
| There were problems deleting from the persistent store for 'appState'. |
|
Cause
| cause |
|
Action
| Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149614
|
Error: There were problems during the server disconnect for listener 'listener'. t
|
Description
| There were problems during the server disconnect for listener 'listener'. t |
|
Cause
| t |
|
Action
| Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149615
|
Error: Unrecognized type: 'name'.
|
Description
| Unrecognized type: 'name'. |
|
Cause
| Unrecognized type: 'name'. |
|
Action
| Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149616
|
Error: A critical internal application name was not deployed. Error: message
|
Description
| A critical internal application name was not deployed. Error: message |
|
Cause
| Unknown |
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis. |
|
|
BEA-149617
|
Warning: Non-critical internal application name was not deployed. Error: message
|
Description
| Internal Application name was not deployed. Application may not have been installed. |
|
Cause
| Internal Application may not have been installed. |
|
Action
| Install WLS internal Application by running WLS installer and choosing the relevent option. |
|
|
BEA-149618
|
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-149619
|
Error: The delete of configuration file filename failed.
|
Description
| During an activate, the configuration file could not be deleted. The file was marked to be deleted on server exit, but this may also fail. |
|
Cause
| An error occurred while deleting the file. |
|
Action
| Ensure that no processes have the file open for write. Ensure that the permissions on the directory allow for delete of this file. |
|
|
BEA-149620(retired)
|
Warning: The configuration file configurationName is read only.
|
Description
| Write access to file configurationName is disabled, so changes to the configuration will not be saved to disk. |
|
Cause
| This occurs when the write permissions on the file are not set to allow the user that booted the server to write to the config.xml file. Write access is often intentionally denied in production environments. |
|
Action
| In many cases, write access is intentionally denied. In such cases, this is just an informational message. If the file needs to be writable, change the permissions on the file or ask your system administrator to do so if you cannot. |
|
|
BEA-149621
|
Error: Error occurred while admin server performing config recovery. Error is : 'theError'
|
Description
| Error occurred while admin server performing config recovery. Error is : 'theError' |
|
Cause
| See the exception details for the cause. |
|
Action
| Stop the server and do config recovery manually. |
|
|
BEA-149622
|
Error: Could not get file lock used to serialize access to configuration files.
|
Description
| Before reading or writing files to the pending or config directories, the deployment subsystem obtains a file lock to ensure that no other thread is writing to a file at the same time as it is being read. |
|
Cause
| Lock could not be obtained before the specified timeout period has elapsed. |
|
Action
| Verify the configuration files and ensure no server has hung, thereby not releasing the lock. |
|
