|
BEA-290000(retired)
|
Error: Error occurred in the deployment service servlet, and received an unacceptable request of type "request0".
|
Description
| The deployment service servlet of the Admin Server was unable to handle the request of type "request0", as it is an invalid request type not currently supported.
|
|
Cause
| An invalid request has been made to the deployment service servlet.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290001
|
Error: Error occurred in the deployment service servlet, and received an unacceptable request of type "request0" with content type "request1".
|
Description
| The deployment service servlet of the Admin Server was unable to handle the request of type "request0" with content type "request1", as it is an invalid content type for post request.
|
|
Cause
| An invalid request has been made to the deployment service servlet.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290002(retired)
|
Error: No application specified with "request0". Deployment service servlet received an unacceptable request for the application "request0".
|
Description
| The deployment service servlet of the Admin Server was unable to handle the request for the application "request0", as there is no such application available.
|
|
Cause
| An invalid request has been made to the deployment service servlet.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290003
|
Warning: Deployment service servlet encountered an exception while handling request of type "request0". Exception is: "request1".
|
Description
| Deployment service servlet of the Admin Server was unable to handle the request of type "request0", as there is an exception occurred. Exception is: "request1".
|
|
Cause
| Error occurred while handling the request.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290004(retired)
|
Warning: Deployment service servlet encountered an Exception while handling the deployment service message from "request0". Exception is: "request1".
|
Description
| Deployment service servlet encountered an Exception while handling the deployment service message from "request0" . Exception is: "request1".
|
|
Cause
| Error occurred while handling the deployment service message request.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290005(retired)
|
Warning: Deployment service servlet encountered an Exception while retrieving application "request0" . Exception is: "request1".
|
Description
| Deployment service servlet encountered an Exception while retrieving application "request0". Exception is: "request1".
|
|
Cause
| Error occurred while retrieving application
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290006
|
Warning: Deployment service servlet received a request of type "request0" with no application name.
|
Description
| Deployment service servlet received a request of type "request0" with no application name. Required application name.
|
|
Cause
| Invalid deployment service servlet request.
|
|
Action
| Requires application name
|
|
|
BEA-290007
|
Warning: Deployment service servlet unable to find upload directory while handling request of type "request0" for application "requst1".
|
Description
| Deployment service servlet unable to find upload directory while handling request of type "request0" for application "requst1".
|
|
Cause
| Unable to find upload directory.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290008
|
Warning: Deployment service servlet encountered while extracting uploaded file to directory "request0". Exception is: "requst1".
|
Description
| Deployment service servlet encountered while extracting uploaded file to directory "request0". Exception is: "requst1".
|
|
Cause
| Exception while extracting uploaded file.
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290009
|
Warning: Deployment service servlet failed to get initialized due to unavailable security service.
|
Description
| Security service is not available while Deployment service servlet is initializing
|
|
Cause
| none
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290010
|
Warning: Deployment service servlet failed to get initialized due to privileged action violation. Exception is: "request0".
|
Description
| Deployment service servlet failed to get initialized due to privileged action violation. Exception is: "request0".
|
|
Cause
| none
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290011
|
Warning: Unauthorized request of type "request0" for user "request1"
|
Description
| Unauthorized request or type "request0" for user "request1"
|
|
Cause
| User is unauthorized for downloading files.
|
|
Action
| Check the user and try again with authorized user.
|
|
|
BEA-290012
|
Warning: Deployment service servlet received jspRefresh request with no upload file name.
|
Description
| Deployment service servlet received jspRefresh request with no upload file name.
|
|
Cause
| Request parameter adminAppPath is null
|
|
Action
| jspRefresh request should provide adminAppPath as upload file name
|
|
|
BEA-290013
|
Warning: No user name or password provided for the request.
|
Description
| Deployment service servlet received request with no user name or password.
|
|
Cause
| User name or password are null.
|
|
Action
| This request requires authentication.
|
|
|
BEA-290014
|
Warning: Invalid user name or password.
|
Description
| Deployment service servlet received request with an invalid user name or password.
|
|
Cause
| Invalid user name or password.
|
|
Action
| Try again with proper user name and password.
|
|
|
BEA-290015
|
Warning: Domain wide secret mismatch
|
Description
| Deployment service servlet received request with an invalid signature.
|
|
Cause
| Invalid signature
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290016
|
Warning: Access not allowed for server "request0" on boot.
|
Description
| Access not allowed for server "request0" on boot.
|
|
Cause
| none
|
|
Action
| This is an internal error. No action is required.
|
|
|
BEA-290017(retired)
|
Warning: Deployment service servlet received file download request for file "request0" and no such file exist.
|
Description
| Deployment service servlet received file download request for file "request0" and no such file exist.
|
|
Cause
| No such file exist.
|
|
Action
| Enter valid file name for download.
|
|
|
BEA-290018(retired)
|
Warning: Deployment service servlet received descriptor download request "request0" for the application "request1" and it is not a valid application that contains requested descriptor.
|
Description
| Deployment service servlet received descriptor download request "request0" for the application "request1" and it is not a valid application that contains requested descriptor.
|
|
Cause
| Wrong application type for given descriptor download request.
|
|
Action
| Try with a valid application name.
|
|
|
BEA-290019(retired)
|
Warning: Deployment service servlet received descriptor download request "request0" for the application "request1" and no such descriptor exists in the application.
|
Description
| Deployment service servlet received descriptor download request "request0" for the application "request1" and no such descriptor exists in the application.
|
|
Cause
| No such descriptor exist.
|
|
Action
| Check the application and descriptor if they are correct
|
|
|
BEA-290020
|
Error: Exceptions encountered while invoking application lifecycle listeners
|
Description
| Server log will contain additional information
|
|
Cause
| A registered lifecycle listener detected an error
|
|
Action
| Depends on the error.
|
|
|
BEA-290021
|
Error: path does not exist
|
Description
| File access failed
|
|
Cause
| File does not exist on admin server
|
|
Action
| None required
|
|
|
BEA-290022
|
Error: This request needs to be initiated through a start control
|
Description
| Internal protocol error
|
|
Cause
| Protocol error
|
|
Action
| None required
|
|
|
BEA-290023(retired)
|
Error: This request needs to be initiated through a start control
|
Description
| Internal protocol error
|
|
Cause
| Protocol error
|
|
Action
| None required
|
|
|
BEA-290024
|
Error: Deployment type cb has already been registered with the DeploymentService
|
Description
| The deployment failed due to an internal error.
|
|
Cause
| Internal error
|
|
Action
| None required
|
|
|
BEA-290025
|
Error: Cannot call ''start()'' when DeploymentRequest has already been started
|
Description
| Invalid state transition
|
|
Cause
| Internal error
|
|
Action
| None required
|
|
|
BEA-290026
|
Info: request 'id' is in 'state' state - request has already been cancelled
|
Description
| Request has already been cancelled
|
|
Cause
| Request has already been cancelled
|
|
Action
| None required
|
|
|
BEA-290027
|
Info: request 'id' is in 'state' state - it is too late to attempt cancelling it
|
Description
| The request is being committed and can not be cancelled
|
|
Cause
| The request is being committed and can not be cancelled
|
|
Action
| None required
|
|
|
BEA-290028
|
Info: deployment 'id' has been cancelled
|
Description
| The request has already been cancelled
|
|
Cause
| The request has already been cancelled
|
|
Action
| None required
|
|
|
BEA-290029
|
Info: deployment 'id' timed out on admin server
|
Description
| The deployment has timed out. Unable to cancel it
|
|
Cause
| The request has timed out
|
|
Action
| None required
|
|
|
BEA-290030
|
Error: No data handler registered for type 'type'
|
Description
| No handler for this protocol has been registered
|
|
Cause
| No handler for this protocol has been registered
|
|
Action
| None required
|
|
|
BEA-290031
|
Error: No tasks associated with this deployment request that can be cancelled
|
Description
| No cancellable tasks exists for this request
|
|
Cause
| Tasks have already completed
|
|
Action
| None required
|
|
|
BEA-290032
|
Error: Data Transfer Handler exists for handler type: 'type'
|
Description
| Handlers are registered for different transfer protocols.
|
|
Cause
| The handler type is already registered
|
|
Action
| None required
|
|
|
BEA-290033(retired)
|
Warning: Deployment service servlet received planDir download request "request0" for the application "request1" and it is not a valid application that contains plan directory.
|
Description
| Deployment service servlet received planDir download request "request0" for the application "request1" and it is not a valid application that contains plan directory.
|
|
Cause
| Wrong application type for given plan directory download request.
|
|
Action
| Try with a valid application name.
|
|
|
BEA-290034(retired)
|
Warning: Deployment service servlet received planDir download request "request0" for the application "request1" and no such requested directory "request2" no exist.
|
Description
| Deployment service servlet received planDir download request "request0" for the application "request1" and no such requested directory "request2" no exist.
|
|
Cause
| The requested application may not contain plan directory.
|
|
Action
| Try with a valid application name.
|
|
|
BEA-290035(retired)
|
Warning: Deployment service servlet received planDir download request "request0" for the application "request1" and plan directory not configured for this application.
|
Description
| Deployment service servlet received planDir download request "request0" for the application "request1" and plan directory not configured for this application.
|
|
Cause
| The requested application does not have plan directory configured.
|
|
Action
| Try with a valid application name.
|
|
|
BEA-290036
|
Warning: Deployment for request id 'request0' is deferred since target 'request1' is disconnected.
|
Description
| Deployment for request id 'request0' is deferred since target 'request1' is disconnected.
|
|
Cause
| Target server 'request1' is disconnected.
|
|
Action
| None
|
|
|
BEA-290038(retired)
|
Error: The download type 'type' is invalid. This download is only valid for the plan, alternate deployment descriptor, alternate WLS deployment descriptor, application.xml, or weblogic-application.xml files.
|
Description
| The download type 'type' is invalid. This download is only valid for the plan, alternate deployment descriptor, alternate WLS deployment descriptor, application.xml, or weblogic-application.xml files.
|
|
Cause
| The download type 'type' is invalid. This download is only valid for the plan, alternate deployment descriptor, alternate WLS deployment descriptor, application.xml, or weblogic-application.xml files.
|
|
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-290039
|
Error: Unrecognized Callback
|
Description
| Unrecognized Callback
|
|
Cause
| Unrecognized Callback
|
|
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-290040
|
Error: The cancel call cannot be completed at this point because the deployment request 'id' has already been partially committed.
|
Description
| The cancel call cannot be completed at this point because the deployment request 'id' has already been partially committed.
|
|
Cause
| A cancel was requested on a committed deployment task.
|
|
Action
| Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
|
|
|
BEA-290041
|
Warning: Commit failed message received for id: 'id' that has no request - it may be completed or cancelled - sending commit succeeded message anyway.
|
Description
| Commit failed message received for id: 'id' that has no request - it may be completed or cancelled - sending commit succeeded message anyway.
|
|
Cause
| Commit failed message received for id: 'id' that has no request - it may be completed or cancelled - sending commit succeeded message anyway.
|
|
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-290042
|
Warning: Received a commit message call without a corresponding request - it may have been completed or cancelled - sending commit failed message.
|
Description
| Received a commit message call without a corresponding request - it may have been completed or cancelled - sending commit failed message.
|
|
Cause
| Received a commit message call without a corresponding request - it may have been completed or cancelled - sending commit failed message.
|
|
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-290043
|
Warning: Cancel failure encountered when attempting to cancel 'id' due to optimistic concurrency violation
|
Description
| Cancel failure encountered when attempting to cancel 'id' due to optimistic concurrency violation
|
|
Cause
| Cancel failure encountered when attempting to cancel 'id' due to optimistic concurrency violation
|
|
Action
| Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
|
|
|
BEA-290044
|
Info: operation delivery
|
Description
| operation delivery
|
|
Cause
| operation delivery
|
|
Action
| None
|
|
|
BEA-290045
|
Info: prepare
|
Description
| prepare
|
|
Cause
| prepare
|
|
Action
| None
|
|
|
BEA-290046
|
Info: commit
|
Description
| commit
|
|
Cause
| commit
|
|
Action
| None
|
|
|
BEA-290047
|
Info: cancel
|
Description
| cancel
|
|
Cause
| cancel
|
|
Action
| None
|
|
|
BEA-290048
|
Error: Request with id 'id' timed out.
|
Description
| Request with id 'id' timed out.
|
|
Cause
| Request with id 'id' timed out.
|
|
Action
| Try increasing the deployment timeout value. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-290049
|
Warning: Deploy failed for id 'id' since no targets are reachable.
|
Description
| Deploy failed for id 'id' since no targets are reachable.
|
|
Cause
| Deploy failed for id 'id' since no targets are reachable.
|
|
Action
| Ensure targeted servers are alive and available from admin server.
|
|
|
BEA-290050
|
Error: Failed to deliver commit message to the following targets 'targets'.
|
Description
| Failed to deliver commit message to the following targets 'targets'.
|
|
Cause
| Failed to deliver commit message to the following targets 'targets'.
|
|
Action
| Ensure targeted servers are alive and available from admin server. 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-290051
|
Error: The commit message for the deployment 'id' could not be completed because the deployment timed out.
|
Description
| The commit message for the deployment 'id' could not be completed because the deployment timed out.
|
|
Cause
| The commit message for the deployment 'id' could not be completed because the deployment timed out.
|
|
Action
| Try increasing the deployment timeout value. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-290052
|
Info: operation timeout
|
Description
| operation timeout
|
|
Cause
| operation timeout
|
|
Action
| None
|
|
|
BEA-290053
|
Error: Request with id 'id' timed out on admin server.
|
Description
| Request with id 'id' timed out on admin server.
|
|
Cause
| Request with id 'id' timed out on admin server.
|
|
Action
| Try increasing the deployment timeout value. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-290054
|
Info: Deployment request 'id' was explicitely cancelled.
|
Description
| Deployment request 'id' was explicitely cancelled.
|
|
Cause
| Deployment request 'id' was explicitely cancelled.
|
|
Action
| None
|
|
|
BEA-290055
|
Warning: Deployment request 'id' timed out on the admin server during 'operation'.
|
Description
| Deployment request 'id' timed out on the admin server during 'operation'.
|
|
Cause
| Deployment request 'id' timed out on the admin server during 'operation'.
|
|
Action
| Try increasing the deployment timeout value. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-290056
|
Info: indeterminate
|
Description
| indeterminate
|
|
Cause
| indeterminate
|
|
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-290057
|
Info: Invalid DeploymentRequest - the object returned by the DeploymentService has been modified in an incompatible way
|
Description
| Invalid DeploymentRequest - the object returned by the DeploymentService has been modified in an incompatible way
|
|
Cause
| Invalid DeploymentRequest - the object returned by the DeploymentService has been modified in an incompatible way
|
|
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-290058
|
Error: There is no request corresponding to request id 'id' currently being processed. The request will be canceled if it is received in the future.
|
Description
| There is no request corresponding to request id 'id' currently being processed. The request will be canceled if it is received in the future.
|
|
Cause
| There is no request corresponding to request id 'id' currently being processed. The request will be canceled if it is received in the future.
|
|
Action
| Check that your task id is the task that you would like to cancel.
|
|
|
BEA-290059
|
Error: Operation 'operation' is not one of the supported types when creating a Change Descriptor
|
Description
| Operation 'operation' is not one of the supported types when creating a Change Descriptor
|
|
Cause
| Operation 'operation' is not one of the supported types when creating a Change Descriptor
|
|
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-290060
|
Error: Duplicate registration for 'id'.
|
Description
| Duplicate registration for 'id'.
|
|
Cause
| Duplicate registration for 'id'.
|
|
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-290061
|
Error: UnrecognizedTypes: 'name1', 'name2'.
|
Description
| UnrecognizedTypes: 'name1', 'name2'.
|
|
Cause
| UnrecognizedTypes: 'name1', 'name2'.
|
|
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-290062
|
Error: The server configuration is out of date with the domain configuration and an attempt to synchronize with the admin server failed. This server needs to be restarted to enable it to synchronize with the domain configuration.
|
Description
| The server configuration is out of date with the domain configuration and an attempt to synchronize with the admin server failed. This server needs to be restarted to enable it to synchronize with the domain configuration.
|
|
Cause
| The server configuration is out of date with the domain configuration and an attempt to synchronize with the admin server failed. This server needs to be restarted to enable it to synchronize with the domain configuration.
|
|
Action
| If a restart of the server does not resolve the problem and the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-290063
|
Info: commit for request 'id' will not proceed further since its requires restart flag is set.
|
Description
| The commit phase of the request requires a restart for it to proceed further.
|
|
Cause
| The commit phase of the request requires a restart for it to proceed further.
|
|
Action
| Requires the restart of either the server or a system resource that is part of the request.
|
|
|
BEA-290064
|
Warning: Deployment service servlet encountered an Exception while handling the deployment service message for request id "requestId" from server "srcServer". Exception is: "message".
|
Description
| Deployment service servlet encountered an Exception while handling the deployment service message for request id "requestId" from server "srcServer". Exception is: "message".
|
|
Cause
| Error occurred while handling the deployment service message request.
|
|
Action
| This is an internal error. Please look at the log file for more details.
|
|
|
BEA-290065
|
Warning: Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "requestId" from server "srcServer". Exception is: "message".
|
Description
| Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "requestId" from server "srcServer". Exception is: "message".
|
|
Cause
| Error occurred while handling the deployment datatransfer request.
|
|
Action
| This is an internal error. Please look at the log file for more details.
|
|
|
BEA-290066
|
Warning: Error occurred while downloading files from admin server for deployment request "requestId". Underlying error is: "errorMessage"
|
Description
| Error occurred while downloading files from admin server for deployment request "requestId". Underlying error is: "errorMessage"
|
|
Cause
| indeterminate
|
|
Action
| indeterminate
|
|
|
BEA-290067
|
Warning: Deployment request 'requestId' was cancelled because servers: 'servers' were unreachable and the domain has cluster-constraints-enabled set to true. To deploy to this cluster, either start the unreachable servers or remove the unreachable servers from the cluster, then reattempt the deployment. If this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the admin server. This allows you to deploy the application only to those servers that can be reached.
|
Description
| A deployment request to a cluster that does not have all its member servers active is rejected when the domain is configured with cluster-constraints-enabled set to true.
|
|
Cause
| Not all the servers in the cluster are running and cluster-constraints-enabled is set to true
|
|
Action
| Start all the servers in the cluster and try deployment again, or if this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the admin server.
|
|
