63 lines
6.4 KiB
INI
63 lines
6.4 KiB
INI
prefix=WL
|
|
messagedetail149601=The deployment framework resume failed.
|
|
cause149601=This is an internal server error.
|
|
action149601=Report to error to Oracle Customer Support.
|
|
messagedetail149603=The deployment framework failed to shutdown cleanly.
|
|
cause149603=This is an internal error.
|
|
action149603=Report to this error to Oracle Customer Support.
|
|
messagedetail149605=Some error was found in the AppDeploymentMBean.
|
|
cause149605=Some error was found in the AppDeploymentMBean.
|
|
action149605=Reconfigure AppDeploymentMBean.
|
|
messagedetail149606=Some error was found in configuring deployment mbean.
|
|
cause149606=Some error was found in configuring deployment mbean.
|
|
action149606=Review the application and reconfigure it.
|
|
messagedetail149607=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.
|
|
cause149607=Please see exception.
|
|
action149607=Please see exception. You should undeploy and deploy after correcting the problem.
|
|
messagedetail149608=Unknown type of deployable: ''{0}''
|
|
cause149608=Unknown type of deployable: ''{0}''
|
|
action149608=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 Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149609=AppRuntimeStateRuntime only available on admin server
|
|
cause149609=AppRuntimeStateRuntime only available on admin server
|
|
action149609=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 Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149610=There were problems creating the persistent store.
|
|
cause149610=The exception thrown: {0}
|
|
action149610=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 Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149611=There were problems reading from the persistent store.
|
|
cause149611=The exception thrown: {0}
|
|
action149611=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 Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149612=There were problems saving to the persistent store for ''{0}''.
|
|
cause149612={1}
|
|
action149612=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 Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149613=There were problems deleting from the persistent store for ''{0}''.
|
|
cause149613={1}
|
|
action149613=Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149614=There were problems during the server disconnect for listener ''{0}''. {1}
|
|
cause149614={1}
|
|
action149614=Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149615=Unrecognized type: ''{0}''.
|
|
cause149615=Unrecognized type: ''{0}''.
|
|
action149615=Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149616=A critical internal application {0} was not deployed. Error: {1}
|
|
cause149616=Unknown
|
|
action149616=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 Oracle Customer Support and provide the stack trace for further analysis.
|
|
messagedetail149617=Internal Application {0} was not deployed. Application may not have been installed.
|
|
cause149617=Internal Application may not have been installed.
|
|
action149617=Install WLS internal Application by running WLS installer and choosing the relevent option.
|
|
messagedetail149618=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.
|
|
cause149618=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.
|
|
action149618=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 Oracle Customer Support.
|
|
messagedetail149619=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.
|
|
cause149619=An error occurred while deleting the file.
|
|
action149619=Ensure that no processes have the file open for write. Ensure that the permissions on the directory allow for delete of this file.
|
|
messagedetail149621=Error occurred while admin server performing config recovery. Error is : ''{0}''
|
|
cause149621=See the exception details for the cause.
|
|
action149621=Stop the server and do config recovery manually.
|
|
messagedetail149622=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.
|
|
cause149622=Lock could not be obtained before the specified timeout period has elapsed.
|
|
action149622=Verify the configuration files and ensure no server has hung, thereby not releasing the lock.
|
|
messagedetail149623=Creation of DeploymentManagerMBean failed.
|
|
cause149623=This may occur if an error at the JMX level exists.
|
|
action149623=Report this problem to Oracle Customer Support.
|
|
|