How to mount a WD Book Live as NFS in OEL6U3

BPEL Deployment Exceptions ORABPEL 05200 - 05251
Deployment Exceptions 05200 - 05251

ORABPEL-05200
severity: 10
type: error
name: Cannot read timestamp file
description: An exception occured while attempting to read the timestamp file \"{0}\". The exception reported is: {1}

ORABPEL-05201
severity: 10
type: error
name: Cannot write timestamp file
description: An exception occured while attempting to write the timestamp file \"{0}\". The exception reported is: {1}

ORABPEL-05202
severity: 10
type: error
name: Error opening BPEL archive
description: An exception occured while attempting to open the BPEL archive \"{0}\". The exception reported is: {1}

ORABPEL-05203
severity: 10
type: error
name: Error unpacking BPEL archive
description: An exception occured while attempting to unpack the BPEL archive \"{0}\". The exception reported is: {1}

ORABPEL-05204
severity: 10
type: error
name: Inconsistent process id/revision.
description: The process identifier \"{0}\" and revision tag \"{1}\" do not match the identifier \"{2}\" and revision tag \"{3}\" specified in the process descriptor.
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process.

ORABPEL-05205
severity: 10
type: error
name: Missing BPEL archive file
description: The process domain cannot locate the BPEL archive for process \"{0}\", revision \"{1}\".
fix: If you have deployed the process please check that it is located in the directory \"{2}\".

ORABPEL-05206
severity: 10
type: error
name: Missing BPEL archive file name
description: The name for the BPEL archive file is empty.

ORABPEL-05207
severity: 10
type: error
name: Error deploying BPEL archive
description: An error occurred while attempting to deploy the BPEL archive file \"{0}\"; the exception reported is: {1}

ORABPEL-05208
severity: 10
type: error
name: Missing process descriptor file
description: The process deployment descriptor file \"bpel.xml\" has not been packaged in the BPEL archive \"{0}\".
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process. The BPEL archive \"{0}\" may have been generated with an older version of \"bpelc\".

ORABPEL-05209
severity: 10
type: error
name: Missing BPEL manifest attribute
description: The manifest for BPEL archive \"{0}\" does not contain the required attribute \"{1}\".
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process.

ORABPEL-05210
severity: 10
type: error
name: No BPEL archive files
description: The process domain cannot locate any BPEL archives for process \"{0}\".
fix: If you have deployed a process please check that it is located in the directory \"{1}\".

ORABPEL-05211
severity: 10
type: error
name: Null BPEL manifest
description: The BPEL archive \"{0}\" does not contain a manifest. All deployed BPEL archives must contain a manifest.
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process.

ORABPEL-05212
severity: 10
type: error
name: Deployment directory not found
description: The directory \"{0}\" is expected to be present in the domain directory \"{1}\". The deployed processes for this domain are expected to reside in this directory.
fix: Please ensure that the directory \"{0}\" exists under the domain directory \"{1} \".

ORABPEL-05213
severity: 10
type: error
name: Invalid process id
description: The process identifier \"{0}\" for the BPEL Process archive \"{1}\" is not valid. Process identifiers may start with a letter, a \"$\" or \"_\" character; process characters (other than the first character) include a letter, a digit, a \"$\", a \"_\" or \"-\" character.
fix: Please make sure that the deployment descriptor contained in the BPEL Process archive \"{1}\" has a valid process id.

ORABPEL-05214
severity: 10
type: error
name: Invalid process revision tag
description: The process revision tag \"{0}\" for the BPEL Process archive \"{1}\" is not valid. Valid revision tags may contain the following characters: a letter, a digit or any of [\"$\", \"_\", \"-\", \".\"].
fix: Please make sure that the deployment descriptor contained in the BPEL Process archive \"{1}\" has a valid revision tag.

ORABPEL-05215
severity: 5
type: error
name: Error while loading process
description: The process domain encountered the following errors while loading the process \"{0}\" (revision \"{1}\"): {2}.
fix: If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.

ORABPEL-05216
severity: 10
type: error
name: Process class not valid
description: The class \"{0}\" for the process \"{1}\" (revision \"{2}\") does not implement the ICubeProcess interface. All process classes contained within the process domain must implement this interface.
fix: Please try recompiling your BPEL process again. The current BPEL process archive \"{1}\" may have been compiled with an older version of \"bpelc\".

ORABPEL-05217
severity: 10
type: error
name: Error while creating process
description: An error has occurred while attempting to instantiate the class \"{0}\" for the process \"{1}\" (revision \"{2}\"). The exception reported was: {3}
fix: Please try recompiling your BPEL process again. The current BPEL process archive \"{1}\" may have been compiled with an older version of \"bpelc\".

ORABPEL-05220
severity: 10
type: error
name: Unknown process classname
description: The process \"{0}\" (revision \"{1}\") is missing its classname; this element cannot be created without its classname.

ORABPEL-05221
severity: 10
type: error
name: Error while updating process
description: An error has occurred while attempting to update the process descriptor for the BPEL process \"{0}\" (revision \"{1}\"). The exception reported was: {2}

ORABPEL-05222
severity: 10
type: error
name: Type class not found
description: Cannot find class for type \"{0}\". Please check that the class is located in the classpath.

ORABPEL-05223
severity: 10
type: error
name: Type excluded
description: Cannot generate type helpers for the class \"{0}\". This class cannot be persisted by the BPEL process domain. Objects which maintain system level handles cannot be persisted and recreated reliably.

ORABPEL-05224
severity: 10
type: error
name: Insufficient security priviledges
description: Failed to generate persistence manager \"{0}\" for class \"{1}\". The application server reflection access check must be disabled in order for the persistence manager to be created. If you cannot disable this check, you must implement your own persistence manager for the class \"{1}\".

ORABPEL-05225
severity: 10
type: error
name: Invalid persistence manager class
description: The persistence manager class \"{0}\" for type \"{1}\" does not implement the IPersistenceManager interface.

ORABPEL-05226
severity: 10
type: error
name: Error while creating persistence manager
description: An error occurred while attempting to instantiate the persistence manager class \"{0}\" for type \"{1}\". The exception reported was: {2}

ORABPEL-05227
severity: 10
type: error
name: Invalid deserializer class
description: The Axis deserializer class \"{0}\" for type \"{1}\" does not implement the Deserializer interface.

ORABPEL-05228
severity: 10
type: error
name: Invalid serializer class
description: The Axis serializer class \"{0}\" for type \"{1}\" does not implement the Serializer interface.

ORABPEL-05229
severity: 10
type: error
name: Error while creating serializers
description: An error occurred while attempting to instantiate the Axis serializer class \"{0} \" for type \"{1}\". The exception reported was: {2}.

ORABPEL-05230
severity: 10
type: error
name: Error accessing working directory
description: Cannot access type working directory \"{0}\". This directory is used by the BPEL process domain to generate helper classes for types used in a process.
fix: Please check that the directory \"{0}\" is readable and writable by the BPEL process domain.

ORABPEL-05231
severity: 10
type: error
name: Error while creating working directory
description: Cannot create type working directory \"{0}\". This directory is used by the BPEL process domain to generate helper classes for types used in a process.
fix: Please check that the directory \"{0}\" exists and is readable and writable by the BPEL process domain.

ORABPEL-05232
severity: 10
type: error
name: Error while creating working directory
description: Cannot create type working directory \"{0}\". This directory is used by the BPEL process domain to generate helper classes for types used in a process. The exception reported is: \"{1}\".
fix: Please check that the directory \"{0}\" exists and is readable and writable by the BPEL process domain.

ORABPEL-05233
severity: 5
type: error
name: Mail account not found
description: The mail account \"{0}\" cannot be found in the metadata directory.

ORABPEL-05234
severity: 10
type: error
name: Error creating mail account
description: An exception occured while attempting to parse the mail account from the XML file \"{0}\". The exception reported is: {1}

ORABPEL-05235
severity: 10
type: error
name: Error unpacking task template archive
description: An exception occured while attempting to unpack the task template archive \"{0}\". The exception reported is: {1}

ORABPEL-05236
severity: 10
type: error
name: Error while creating task template
description: An error has occurred while attempting to instantiate the class \"{0}\" for the task template \"{1}\" (archive \"{2}\"). The exception reported was: {3}

ORABPEL-05237
severity: 5
type: error
name: Task template not found
description: The task template \"{0}\" cannot be found in the metadata directory.

ORABPEL-05238
severity: 10
type: error
name: Tasklet class not valid
description: The class \"{0}\" for the task template \"{1}\" does not implement the ITasklet interface. All tasklet classes contained within the process domain must implement this interface.
fix: Please try regenerating your task template archive again.

ORABPEL-05239
severity: 5
type: error
name: JMS connector not found
description: The jms connector \"{0}\" cannot be found in the metadata directory.

ORABPEL-05240
severity: 10
type: error
name: Error creating jms connector
description: An exception occured while attempting to parse the jms connector from the XML file \"{0}\". The exception reported is: {1}

ORABPEL-05241
severity: 10
type: error
name: Missing task descriptor
description: The task descriptor file \"task.xml\" for the task template \"{0}\" has not been packaged in the task archive file \"{1}\".

ORABPEL-05242
severity: 10
type: error
name: Invalid suitcase deployment descriptor
description: The suitcase descriptor of bpel archive \"{0}\" is not valid.
fix: Rebuild your suitcase and redeploy it using the current BPEL build environment.

ORABPEL-05243
severity: 10
type: error
name: Cannot obtain lock for process
description: Failed to obtain load lock for process \"{0}\"; exception reported is: {1}

ORABPEL-05244
severity: 10
type: error
name: Timed out waiting for process load lock
description: Failed to obtain load lock for process \"{0}\"; timed out after {1} seconds.

ORABPEL-05245
severity: 10
type: error
name: Cannot extract process descriptor
description: Failed to write descriptor file for process \"{0}\", revision \"{1}\"; exception reported is: {2}

ORABPEL-05246
severity: 10
type: error
name: Cannot marshall process descriptor
description: Failed to marshall descriptor for process \"{0}\", revision \"{1}\"; exception reported is: {2}

ORABPEL-05247
severity: 5
type: error
name: Process not found
description: The BPEL process with GUID \"{0}\" has not been loaded. Either the process was not initialized properly or the process has been disabled.
fix: Please consult your administrator regarding this error. The application server logs may provide more information regarding this error.

ORABPEL-05248
severity: 5
type: error
name: Cannot read process bytes
description: An exception occured while attempting to read the bytes from BPEL archive \"{0}\". The exception reported is: {2}

ORABPEL-05249
severity: 10
type: error
name: Cannot compute process guid
description: Failed to compute guid for process \"{0}\", revision \"{1}\"; exception is: {2}

ORABPEL-05250
severity: 10
type: error
name: Error deploying BPEL suitcase
description: An error occurred while attempting to deploy the BPEL suitcase file \"{0}\"; the exception reported is: {1}

ORABPEL-05251
severity: 10
type: error
name: Cannot compute suitcase checksum
description: Failed to compute suitcase id; exception is: {0}