The ConfigFwk catalog contains messages in the range
BEA390001 - BEA391499. Messages in this catalog are part of the
com.bea.wli.config.messages Internationalization package and the
com.bea.wli.config.messages Localization package.
|
BEA-390001
|
Info: Reference to a non-existing instance: ref
|
Cause
| A resource has a reference to another resource which does not exist. |
|
Action
| Import or create the missing resource, or remove the reference by updating the referent accordingly. |
|
|
BEA-390002
|
Info: Resource ref forms a cyclic reference
|
Cause
| There is a chain of references involving two or more resources that form a cyclic dependency. Certain chains may be allowed, depending on the resources on the chain. |
|
Action
| If the cyclic reference chain is preventing session activation, break the chain by removing one of references. |
|
|
BEA-390003
|
Error: Child resource ref is not associated with a parent resource
|
|
BEA-390004
|
Error: Child resource ref is associated with more than one parent resource
|
Cause
| More than one resource instance contains a reference to a child instance. Instances of resources that are defined as Child types can only be references by instances of resources that are defined as Parent types, through parent-child references. Update references in the parent instances or delete one of the parent instances so that only one has a child reference to the child resource. |
|
|
BEA-390005
|
Error: Dangling child reference from parent to child
|
|
BEA-390006
|
Error: Parent resource parent has multiple containments of child resource child. Containment names: names
|
Description
| A parent resource can reference a child resource only once. |
|
|
BEA-390007
|
Error: Instance of class expected was expected as resource data, but found class found
|
Cause
| Illegal data was provided when updating or creating a resource |
|
Action
| Make sure that you provide the correct type of data when creating or updating a resource |
|
|
BEA-390008
|
Error: ref already exists
|
|
BEA-390009
|
Error: ref does not exist
|
|
BEA-390010
|
Error: Validation of ref failed
|
|
BEA-390013
|
Error: Execution record for the given task was not found
|
Cause
| An attempt is made to undo a previous change, but the information about the change, is not found. No execution record was found with the task id supplied by the user. The task id may be invalid, or the execution record may have been purged by the admin |
|
Action
| Make sure you are using the correct task id. |
|
|
BEA-390014
|
Error: Change has already been undone
|
Cause
| An attempt is made to undo a previous change twice. |
|
Action
| No action is necessary |
|
|
BEA-390015
|
Error: No undo record found for task
|
Cause
| An attempt is made to undo a previous change, but the change cannot be undone. Certain internal changes initiated by the server cannot be undone. |
|
Action
| No action is necessary |
|
|
BEA-390018
|
Error: Undo cannot be completed because the changes have errors. See log file for details
|
Action
| Inspect the error log, and if there are validation errors in resources, attempt to fix them. |
|
|
BEA-390019
|
Error: No exec records for session session
|
Cause
| Unexpected error due to a failed session activation |
|
Action
| Contact technical support |
|
|
BEA-390020
|
Info: Config Service is initializing for the first time
|
|
BEA-390021
|
Info: Creating out-of-the-box location: path
|
|
BEA-390022
|
Info: Creating out-of-the-box resource: path
|
|
BEA-390100
|
Info: Session session is being activated
|
|
BEA-390101
|
Error: Activation of session session failed: t
|
Action
| Inspect the error message and try to fix any validation errors or add systems resources that are missing. |
|
|
BEA-390102
|
Info: Session session was activated successfully
|
|
BEA-390103
|
Error: Failed to discard session session after successful activation: t
|
Action
| Retry the discard operation. |
|
|
BEA-390104
|
Error: Failed to create WLS change list for activation of session session: t
|
Description
| Session activation requires a lock on WLS configuration to perform any deployments that are required by the resources. However the lock could not be obtained |
|
Cause
| Another session activation may be in progress, or another user may have already started a WLS change list and holding the lock. |
|
Action
| If another session activatio is already in progress, wait until the activation finishes. If another user is holding the lock, contact the user. |
|
|
BEA-390105
|
Error: Unable to create WLS change list due to a short term automatic lock obtained by user user. The user has no pending changes and the lock will expire in remainingSeconds seconds. Please try again after the lock has expired.
|
Cause
| Session activation requires a lock on WLS configuration to perform any deployments that are required by the resources. In this case the lock is obtained automatically by WLS console on behalf of the user. The lock is obtained regardless of any changes, and will expire in a short time. |
|
Action
| Wait until the lock expires or the other user explicitly releases the lock, and try again. |
|
|
BEA-390106
|
Error: Failed to cancel WLS change list: t
|
Cause
| An unexpected error occurred when cancelling WLS changes after a failed session activation |
|
Action
| Contact technical support |
|
|
BEA-390108
|
Error: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred: summary
|
Action
| Retry the activation. |
|
|
BEA-390109
|
Error: Failed to notify session listener listener for operation notification on session session
|
Cause
| An unexpected error occured when activating changes. |
|
Action
| Contact technical support |
|
|
BEA-390111
|
Error: Another session operation is in progress. Please retry later.
|
Action
| Retry the session activation after the other activation finishes |
|
|
BEA-390112
|
Error: No session was specified.
|
Cause
| Certain configuration APIs work only in a session, but no session name is passed in the arguments. |
|
Action
| Make sure you provide the session name. |
|
|
BEA-390113
|
Error: Resource resource was not modified in session session, therefore cannot sync to the core data.
|
Description
| If a resource is modified both in a session, and in the core (via the activation of another session), two versions of the resource conflict. The user can either choose to overwrite core changes simply by activating the session, or sync to the core changes, effectively discarding his own changes. |
|
Cause
| An attempt is made to sync to the core changes for a resource that has not been modified in a session. |
|
Action
| Make sure you invoke sync operation on a resource that is modified in the session. |
|
|
BEA-390114
|
Error: Deployed configuration state has changed while creating a session. Please try creating the session again.
|
Action
| Retry session creation. |
|
|
BEA-390115
|
Error: Failed to save WLS changes for session session
|
Cause
| WLS changes that are made in response to a session activation has failed |
|
Action
| Inspect the error messages from WLS and consult WLS documentation |
|
|
BEA-390116
|
Error: Failed to release WLS Edit session lock: t
|
Action
| No action is necessary |
|
|
BEA-390117
|
Error: Failed to instantiate core: t
|
Cause
| Unexpected error |
|
Action
| Contact technical support |
|
|
BEA-390118
|
Error: Failed to instantiate session: session
|
Action
| Retry session creation |
|
|
BEA-390119
|
Error: Failed to set session description: session
|
Action
| Make sure you provided the correct session name |
|
|
BEA-390120
|
Error: Failed to notify session session of core changes: t
|
Cause
| When a session is activated, the changes are propagated to other sessions, causing them to absorb the changes and revalidate their own content if necessary. An unexpected error occured while the changes are propagated. |
|
Action
| Contact technical support |
|
|
BEA-390121
|
Error: Session session already exists
|
Cause
| You are attempting to create a session that already exists. |
|
Action
| When creating a session programmatically, first check if a session with the same name exist. If so you can choose to use it or discard it. When using the console, make sure you are now using a stale view of the configuration by refreshing the page. |
|
|
BEA-390122
|
Error: Cannot create sessioned on a non-admin server
|
Cause
| A programmatic attempt is made to create a session on a server other than the admin. |
|
Action
| Contact technical support |
|
|
BEA-390123
|
Error: session is an invalid session name
|
Description
| Session names can contain java identifier characters, - or .. |
|
Action
| Use a session name that contains only the legal character, namely, java identifier characters, - or . |
|
|
BEA-390124
|
Error: Session session cannot be discarded because it is being activated
|
Cause
| An attempt is made to discard a session that is in the process of being activated |
|
Action
| If the activation is initiated accidentally, wait for the activation to finish successfully and undo the session activation. |
|
|
BEA-390125
|
Error: Session session was not found
|
Action
| Make sure the correct session name is used. |
|
|
BEA-390200
|
Info: No recovery is needed under root root
|
|
BEA-390201
|
Info: Recovery is needed under root root
|
|
BEA-390202
|
Info: Previous transaction was interrupted in 'prepare'. Rolling back the changes
|
|
BEA-390203
|
Info: Previous transaction was interrupted in 'rollback'. Completing the rollback
|
|
BEA-390204
|
Info: Previous transaction was interrupted in 'commit'. Continuing the commit
|
|
BEA-390205
|
Info: Rollback finished successfully
|
|
BEA-390206
|
Error: Rollback failed due to errors
|
Action
| Make sure you have the correct file permissions, or that you have enough space in file system |
|
|
BEA-390207
|
Info: Commit finished successfully
|
|
BEA-390208
|
Error: Commit failed due to errors
|
Action
| Make sure you have the correct file permissions, or that you have enough space in file system |
|
|
BEA-390209
|
Critical: Failed to write to transaction file path
|
Action
| Make sure you have the correct file permissions, or that you have enough space in file system |
|
|
BEA-390210
|
Error: Undo failed
|
|
BEA-390211
|
Error: Transaction victimDesc conflicts with survivorDesc for transactional resource conflictingResource and will be rolledback
|
Cause
| Two configuration changes are performed concurrently and they conflict when attempting to change the same data structure, or resource. One of them will be picked as the victim and rolled back. |
|
Action
| Retry the change that was rolledback |
|
|
BEA-390212
|
Error: Cannot enlist transactional resource resource when transaction is in status state
|
Action
| Retry the operation that caused this error |
|
|
BEA-390213
|
Error: Cannot write transactional resource resource when transaction is in status state
|
Action
| Retry the operation that caused this error |
|
|
BEA-390214
|
Error: No transaction exists
|
Action
| Retry the operation that caused this error |
|
|
BEA-390215
|
Error: No file was found
|
Cause
| Internal error |
|
Action
| Contact technical support |
|
|
BEA-390216
|
Error: Attempting to read from a file that is marked for deletion, file: path
|
Cause
| Internal error |
|
Action
| Contact technical support |
|
|
BEA-390300
|
Error: Startup recoveryFailed
|
Cause
| An attempt from a managed server to synchronize configuration with the admin server has failed. |
|
Action
| Inspect the errors and consult WLS documentation. |
|
|
BEA-390301
|
Error: Failed to commit deployment
|
Action
| Retry the deployment |
|
|
BEA-390302
|
Error: Failed to cancel deployment
|
Cause
| Internal error |
|
Action
| Contact technical support |
|
|
BEA-390303
|
Error: Failed to prepare deployment
|
Cause
| Session activation has failed in its prepare phase |
|
Action
| Inspect the errors and consult the documentation |
|
|
BEA-390501
|
Error: No configuration has been uploaded or previously uploaded jar file has already been imported
|
Cause
| An attempt is made to import an uploaded jar twice. An uploaded jar file is deleted from the internal staging area immediately after an import |
|
Action
| When importing the same jar twice, make sure you upload it for each time you want to import it |
|
|
BEA-390504
|
Error: Invalid jar file
|
Cause
| The jar file that is being imported is not a jar file that was previously exported. |
|
Action
| Make sure you are using a jar file that was previously exported. Check if the jar file is meant to be using for bulk import, and if so, use bulk import feature |
|
|
BEA-390505
|
Error: The jar that is being imported is an unsupported version of the product. The version was failedVersion. Supported versions are: supportedVersionsString
|
Cause
| The jar that is being imported was created using a version of the product that is no longer supported. |
|
Action
| Contact technical support |
|