- CWWBC0001E: The method {0} in class {1} received an unexpected exception; the exception stack trace follows: {2}.
- Explanation: An unchecked exception was caught by the Compensation service.
- User Action: If the cause of the error was not a user error, contact IBM support.
- CWWBC0002E: An internal error occurred in method {0} in class {1}; the exception stack trace follows: {2}.
- Explanation: An internal error was detected in the Compensation service.
- User Action: Contact IBM support.
- CWWBC0003E: The compensation executor is in the {0} state, but the {2} method requires the executor to be in the {1} state.
- Explanation: An attempt was made to invoke a method on the compensation executor. However for that method call to be valid, the executor needs to be in a differentstate from its current state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0004E: The compensation executor is in the {0} state, but the {3} method requires the executor to be in the {1} or {2} states.
- Explanation: An attempt was made to invoke a method on the compensation executor. However for that method call to be valid, the executor needs to be in a differentstate from its current state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0005E: The {0} method is expecting a proceed string of {1}, but was passed {2}.
- Explanation: An attempt was made to invoke a method on the compensation executor. However for that method call to be valid, the executor needs the proceed stringparameter to be as expected. However the value passed on that parameterwas not as expected.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0006E: The compensation coordinator is in the {0} state, but the {2} method requires the coordinator to be in the {1} state.
- Explanation: An attempt was made to invoke a method on the compensation coodinator. However for that method call to be valid, the coordinator needs to be in a differentstate from its current state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0007E: The compensation coordinator is in the {0} state, but the {3} method requires the coordinator to be in the {1} or {2} states.
- Explanation: An attempt was made to invoke a method on the compensation coordinator. However for that method call to be valid, the coordinator needs to be in a differentstate from its current state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0008E: There is no proclet registered for index {0}.
- Explanation: An attempt was made to change a proclet registered with the compensation coodinator. However no proclet was registeredfor the specified index.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0009E: End called for a compensation coordinator whose close behavior is EXECUTOR_INITIATED_COMPENSATION.
- Explanation: The end method on the compensation coordinator was called, but the coordinator was created with a close behaviour ofEXECUTOR_INITIATED_COMPENSATION. The end method is not permitted if the close behavioris EXECUTOR_INITIATED_COMPENSATION.
- User Action: This exception indicates a problem in the compensation support. Contact IBM Support.
- CWWBC0010E: Close called for a compensation coordinator whose close behavior is EXPLICIT_END_ONLY.
- Explanation: The close method on the compensation coordinator was called, but the coordinator was created with a close behaviour ofEXPLICIT_END_ONLY. The close method is not permitted if the close behavioris EXPLICIT_END_ONLY.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0011E: No executor home available for the compensation coordinator to use.
- Explanation: The end method on the compensation coordinator was called, and one or more proclets needed to be invoked (i.e. one or more pieces ofwork need to be compensated). However, the executor home (whichis needed to perform the compensation work) has not been set.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0012E: A CloseBehaviour of {0} was specified, but only EXPLICIT_END_ONLY or INSIDE_CSCOPE is supported.
- Explanation: The begin method on the compensation current was called, but the only supported options are EXPLICIT_END_ONLY and INSIDE_CSCOPE.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0013E: No current compensation scope.
- Explanation: A method was called on the compensation current. This method requires a current compensation scope. Howeverthere is no current compensation scope.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0014E: Resume is not supported.
- Explanation: The resume method was called on the compensation current. This is not a supported operation.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0015E: Suspend is not supported.
- Explanation: The suspend method was called on the compensation current. This is not a supported operation.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0016E: The direction parameter must not be null.
- Explanation: A call to the compensation code was made with a direction parameter of null. This is not allowed.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0017E: The proclet for index {0} cannot be updated. It has already finished.
- Explanation: An attempt has been made to update a proclet with the specified index. However the compensation coordinator has already been askedto commence compensation processing and the original version of the proclet had afinish time and so cannot be updated
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0018E: The transaction used to perform compensation work did not commit and threw {0}.
- Explanation: An attempt was made to perform some compensation work. However the transaction used for that compensation work rolled back insteadof committing.
- User Action: Investigate the cause of the rollback. Once the cause has been resolved use the Process Choreographer Web Client to either instruct the compensation sphere to retrythe affected piece of compensation work or to skip the affected piece ofcompensation work.
- CWWBC0019E: The transaction used to perform compensation work did not commit and threw {0}.
- Explanation: An attempt was made to perform some compensation work. However the transaction used to surround that compensation work made heuristic decisions
- User Action: Investigate the cause of the heuristic decisions. Once the cause has been resolved use the Process Choreographer Web Client to either instruct the compensation sphere to retrythe affected piece of compensation work or to skip the affected piece ofcompensation work.
- CWWBC0020E: Compensation has failed with exception: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation action threw an exception.
- User Action: Investigate the cause of the exception. Once the cause has been resolved either instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0021E: Compensation failed to locate a object due to: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable to locate the necessaryservice due to a problem with the naming service.
- User Action: Investigate the cause of the exception. Once the cause has been resolved use the Process Choreographer Web Client to either instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0022E: Compensation failed to submit asynchronous work due to: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable to submit asynchronouswork due to a problem with the asynchronous beans service.
- User Action: Investigate the cause of the exception. Once the cause has been resolved use the Process Choreographer Web Client to either instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0023E: Compensation is unable to access the compensation scope due to: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable save the compensation scope due to a problemwith the work area service.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0024E: Compensation is unable to locate the coordinator via a home name of {0} due to {1}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable locate the home of the compensation coordinatorto record the compensation work.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0025E: Compensation is unable to locate the standard executor via a home name of {0} due to {1}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable locate the home of the standard executor.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0026E: Compensation is unable to use the provided executor home due to {0}.
- Explanation: An attempt was made to set the executor home for this compensation sphere, but an exception occured when attempting to save that executor home.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0027E: Compensation is unable to communicate with the executor due to {0}.
- Explanation: An attempt was made to communicate with the executor for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0028E: Compensation is unable to communicate with the coordinator due to {0}.
- Explanation: An attempt was made to communicate with the coordinator for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0029E: Compensation is unable to communicate with the executor due to {0}.
- Explanation: An attempt was made to communicate with the executor for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0030E: The compensation coordinator is in the {0} state, but the {4} method requires the coordinator to be in the {1}, {2}, {3} states.
- Explanation: An attempt was made to invoke a method on the compensation coordinator. However for that method call to be valid, the coordinator needs to be in a differentstate from its current state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0031W: Compensation has been automatically performed assuming a REJECT direction.
- Explanation: The close method was called on the compensation current. As part of the processing of the close method, the compensation scope wasautomatically ended by the system. The compensation processing wasperformed assuming a REJECT decision. This is caused because anotherserver was started for the current EJB application which examined thethe current compensation scope during the processing of the closemethod and, as a result, assumed that the current compensation scopeshould have its end processing automaticallyperformed using a REJECT decision as it appeared that the current transactionhas rolled back as a result of transaction recovery. This is a very rare situation.
- User Action: Since the compensation scope has automatically been REJECTed, the enclosing transaction should be marked as rollback only.
- CWWBC0032E: Compensation is unable to locate the home of the transaction session synchronization bean via a home name of {0} due to {1}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable locate the home of the transactionsession synchronization bean, which is used to tie the compensation scope into the scopeof the enclosing transaction.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0033E: The end method of current is only valid if the corresponding begin call specified a close behavior of EXPLICIT_END_ONLY.
- Explanation: The end method on the compensation current was called, but the corresponding begin call did not specify EXPLICT_END_ONLY as its close behaviour.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0034E: A CloseBehaviour of {0} was specified, but only EXPLICIT_END_ONLY is supported.
- Explanation: The start method on the compensation current was called, but the only supported option is EXPLICIT_END_ONLY.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0035E: There is an existing scope.
- Explanation: The resume method on the compensation current was called, but there is already an existing compensation scope.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0036E: Compensation is unable to locate the run proclet session bean via a home name of {0} due to {1}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable locate the home of the run proclet session beanused to perform the compensation work.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0037E: Could not create operation {0} because no binding operation was found.
- Explanation: An attempt was made to create a WSIFOperation for the specified operation. However no binding information was found for the operation.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0040E: Unable to register compensation because an exception occurred. The error was: {0}.
- Explanation: An attempt was made to communicate with the compensation current,but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0041E: Unable to remove registered compensation because an exception occurred. The error was: {0}.
- Explanation: An attempt was made to communicate with the compensation current,but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0042E: Unable to update registered compensation because an exception occurred. The error was {0}.
- Explanation: An attempt was made to communicate with the compensation current,but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0043E: An unexpected exception occurred. The error was {0}.
- Explanation: An attempt was made to update a registered proclet, but an unexpected exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0044E: Unable to save proclet due to: {0}
- Explanation: An attempt was made to update the list of proclets but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0045E: Unable to retrieve Proclet due to: {0}
- Explanation: An attempt was made to read the list of proclets but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0046E: Unable to save synchronization due to: {0}
- Explanation: An attempt was made to update the list of synchronizations but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0047E: Unable to save the direction of the compensation work due to: {0}.
- Explanation: An attempt was made to peform compensation, but the executor was unable to save the direction of the compensation work.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0048E: Unable to save the compensation work due to: {0}.
- Explanation: An attempt was made to peform compensation, but the executor was unable to save the compensation work.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0049E: The compensation executor is unable to update an unfinished proclet due to: {0}.
- Explanation: An attempt was made to update an unfinished proclet, but the compensation executor was unable to save the compensation work.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0050E: The compensation executor cannot retrieve the failed proclet due to {0}.
- Explanation: An attempt was made to retrieve a failed proclet, but the compensation executor is unable to retrieve the failed proclet.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0051E: The compensation executor was unable to save the index of the next proclet to be compensated due to {0}.
- Explanation: An attempt was made to retrieve a failed proclet, but the compensation executor is unable to retrieve the failed proclet.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0052W: A piece of compensation work has failed (the cause of the failure could not be recorded due to: {0}).
- Explanation: An attempt was made to save the reason why a proclet was unable to perform its compensation task. The reason could not be saved, so this message was saved in its place.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0053E: Unable to scan the set of proclets due to: {0}.
- Explanation: An attempt was made to scan the set of proclets to find the next piece of compensation work but the executor was unable to perform the scan.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0054E: Unable to set the compensation direction due to {0}.
- Explanation: An attempt was made to update the direction of the sphere, but the coordinator was unable save the compensation direction.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0055E: Compensation failed to locate a object due to: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable to locate the necessaryservice due to a problem with the naming service.
- User Action: Investigate the cause of the exception. Once the cause has been resolved use the Process Choreographer Web Client toeither instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0056E: Compensation is unable to locate the standard executor via a home name of {0} due to {1}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable locate the home of the standard executor.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0057I: Compensation is starting for ''{0}''.
- Explanation: Compensation processing was requested for the named compensation sphere and the processing of the steps to perform the compensation is now starting.
- User Action: None.
- CWWBC0058I: Compensation has completed for ''{0}''.
- Explanation: Compensation processing was requested for the named compensation sphere and the processing of the steps to perform the compensation has now completed.
- User Action: None.
- CWWBC0059E: Compensation operation ''{0}'' was invoked via WSIF, but the operation generated a fault: {1}.
- Explanation: Compensation invoked the named compensation operation via WSIF, but that operation returned a fault.
- User Action: Investigate the cause of the fault. Once the cause has been resolved use the Process Choreographer Web Client to either instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0060E: Compensation is unable to locate the coordinator for the sphere ''{0}''.
- Explanation: An attempt was made get the coordinator for a sphere. However the compensation service was unable locate a coordinator for this sphere.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0061E: A Compensation operation has failed due to {0}
- Explanation: An operation was exeuted and throw an exception
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0062E: The Sphere can not execute ''{3}'' because of incorrect state of the ''{0}'', which is ''{1}'' state and should be ''{2}'' state.
- Explanation: The sphere is trying to execute a method but either the compensation coordinator, executor or proclet is in the wrong state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0063W: Compensation was unable to locate a classloader for {0} and will wait for the classloader to become available.
- Explanation: Compensation was required for an application, but the classloader for that application is not available. The most likely cause of this message is that the server has been restarted and compensation is being attempted for the affected business process. When the classloader becomes available, compensation will be automatically resumed.
- User Action: If the application has been stopped, start the application.
- CWWBC0064E: The compensation coordinator is in the {0} state, but the {2} method requires the coordinator to be in the {1} state.
- Explanation: An attempt was made to invoke a method on the compensation coodinator. However for that method call to be valid, the coordinator needs to be in a differentstate from its current state.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0065E: The proclet for index {0} cannot be updated. It has already finished.
- Explanation: An attempt has been made to update a proclet with the specified index. However the compensation coordinator has already been askedto commence compensation processing and the original version of the proclet had afinish time and so cannot be updated
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0066E: Unable to register compensation because an exception occurred. The error was: {0}.
- Explanation: An attempt was made to communicate with the compensation current,but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0067E: Compensation has failed with exception: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation action threw an exception.
- User Action: Investigate the cause of the exception. Once the cause has been resolved either instruct the compensation executor toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0068E: The compensation sphere {0} is inaccessible because of database schema changes.
- Explanation: APAR PQ70665 has been applied, but a compensation sphere was active before the APAR was applied. This compensation sphere cannot be processed due tothe database schema changes applied as part of PQ70665.
- User Action: Contact IBM Support.
- CWWBC0069E: Unable to register compensation because a work area partition could not be created. The error was: {0}.
- Explanation: An attempt was made to initialize the compensation component,but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0070E: Unable to register compensation because a work manager could not be created. The error was: {0}.
- Explanation: An attempt was made to initialize the compensation component,but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0071E: The Sphere can not execute ''{1}'' because the ''{0}'' can not be found.
- Explanation: The sphere is trying to execute a method but either the compensation coordinator, executor or proclet can not be found.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0072E: Compensation failed to submit synchronous work due to: {0}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable to submit synchronouswork due to a problem with the asynchronous beans service.
- User Action: Investigate the cause of the exception. Once the cause has been resolved either instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0073E: A Compensation operation on the CScope service has failed due to {0}
- Explanation: An operation on the CScope service was executed and throw an exception
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0074E: Compensation is unable to communicate with the executor due to {0}.
- Explanation: An attempt was made to communicate with the executor for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0075E: Compensation is unable to create the executor facade due to {0}.
- Explanation: An attempt was made to create the executor facade for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0076E: The recovery policy {0} is not supported.
- Explanation: An attempt was made to use a recovery policy that is not supported
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0077E: The compensation input type of {0} is not supported.
- Explanation: An attempt was made to use a compensation input type that is not supported.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0078E: Compensation was unable to retrieve the exception that put the sphere into indoubt.
- Explanation: Compensation was unable to retrieve the exception that put the sphere into indoubt because of either a server failure or a problem with the database.
- User Action: Repair the indoubt compensation sphere via the webclient.
- CWWBC0079E: Failed to retrieve CScope due to {0}.
- Explanation: A method was called on compensation. This methodrequires a CScope to be active, however the CScope could not be retrieved.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0080E: CScope Identifier {0} is invalid for a nested sphere.
- Explanation: The begin method was called on the compensation current. This method requires a newCScope to be active if the nesting behaviour for the sphere is CS_REQUIRES_NEW_UNRELATEThe CScope should be the same for a nested CS_REQUIRES as the parents unless the parentnesting behaviour was CS_SUPPORTS or CS_NOT_SUPPORTED.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0081E: Compensation has located more than one coordinator for the sphere name ''{0}''.
- Explanation: An attempt was made get the coordinator for a sphere. However thecompensation service located more than one coordinator for that sphere. This coulbe a result of there being multiple flows in existence with the same name.
- User Action: Ensure that there are no flows in existence with the same name.If the cause of the error was not a user error, contact IBM Support.
- CWWBC0082E: No object[] was passed to Compensation FFDC DM processing
- Explanation: There are no objects which can be displayed by FFDC.
- User Action: Contact IBM support.
- CWWBC0083E: FFDC DM was passed more than one FFDCStack object.
- Explanation: There should only be one FFDCStack passed to FFDC
- User Action: Contact IBM support
- CWWBC0084E: FFDC DM was passed more than one FFDCStack object.
- Explanation: There should only be one FFDCStack passed to FFDC
- User Action: Check how FFDC was called in the source
- CWWBC0085E: FFDC Compensation DM was passed in something other than an FFDCStack object
- Explanation: The object passed in to FFDC DM was not an FFDCStack object
- User Action: Contact IBM support
- CWWBC0086E: An attempt to register the compensation diagnostic module failed.
- Explanation: one or more packages could not be registered with the FFDC CompensationDiagnosticModule
- User Action: Contact IBM Support.
- CWWBC0087E: Unsupported Proclet type: ''{0}''.
- Explanation: A proclet instance was found to be not of the type that can be handled by the compensation service.
- User Action: This is an internal failure in the compensation service - contact IBM Support.
- CWWBC0088E: Unsupported Nesting Behaviour: ''{0}''.
- Explanation: The compensation service has been called to begin a compensation sphere with an unsupported type of nesting behaviour.
- User Action: The type of nesting behaviour used should be checked, if this is not in error or cannot be verified contact IBM Support.
- CWWBC0089E: Migration could not get a valid executor home.
- Explanation: The ExecutorHome retrieved was not recognised as an OverseableExecutorHome
- User Action: Contact IBM support
- CWWBC0090E: Migration could not get any executor home due to the error: {0}
- Explanation: An ExecutorHome could not be retrieved
- User Action: Contact IBM support
- CWWBC0091E: The compensation service is unavaliable, so migration cannot complete.
- Explanation: The compensation service is not avaliable
- User Action: Check the WAS server is running and that the compensation service is avaliable. Otherwise contact IBM support.
- CWWBC0092E: Migration of executors in state {0} failed due to the error {1}
- Explanation: The compensation migration client could not compensate 50x executors in the {0} state
- User Action: Contact IBM support
- CWWBC0093E: The compensation service is unable to register the state listener because of the following exception: {0}
- Explanation: The compensation service is unable to register the state listener, because of an exception.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0094E: The compensation service is unable to register the state listener because the close behavior of INSIDE_CSCOPE is not supported for this operation.
- Explanation: The compensation service is unable to register the state listener because the close behavior of INSIDE_CSCOPE is not supported for this operation.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0095E: The compensation service is unable lookup the UserCompensationScope.
- Explanation: The compensation service is unable lookup the UserCompensationScope.
- User Action: Check that the CScope service is started else contact IBM Support.
- CWWBC0096E: The compensation service is unable to call the state listeners to inform them of a state change to the {0} because of the following exception: {1}
- Explanation: The compensation service is unable to call the state listeners to inform them of a state change because of an exception.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0097E: The compensation input type of {0} is not supported with compensation input of {1}.
- Explanation: An attempt was made to use a compensation input type and a compensation input value that is not supported.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0098E: The compensation service failed to create a proclet for the undo action: {0} , because of the following exception: {1} .
- Explanation: An attempt was made to create a proclet for the undo action but an exception was thrown.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0099E: The compensation service failed to register a proclet for the undo action: {0} , because of the following exception: {1} .
- Explanation: An attempt was made to register a proclet for the undo action but an exception was thrown.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0100E: The compensation service failed to update a proclet for the undo action: {0} , because of the following exception: {1} .
- Explanation: An attempt was made to update a proclet for the undo action but an exception was thrown.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0101E: Compensation is unable to create the contextual proclet facade for the contextual proclet {0} due to {1}.
- Explanation: An attempt was made to create the contextual proclet facade for this contextual proclet, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0102E: The compensation service was unable to call {0} on the contextual proclet facade due to the following excpetion: {1}.
- Explanation: An attempt was made to call a method on the contextual proclet facade but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0103E: The compensation service is unable to call the state listener because of the following exception: {0}
- Explanation: The compensation service is unable to call the state listener, because of an exception.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0104E: Compensation is unable to locate the contextual proclet bean via a home name of {0} due to {1}.
- Explanation: An attempt was made to perform some compensation work. However the compensation service was unable locate the home of the contextual proclet beanused to perform the compensation work.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0105E: Compensation is unable to delete the contextual proclets with coordinator primary key {0} after compensation due to the following exception: {1}.
- Explanation: An attempt was made to delete the contextual proclets after compensation has completed. However the compensation service was unable delete the contextual proclets due to an excpetion.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0106E: Unable to save the executor in coordinator due to: {0}
- Explanation: An attempt was made to save the executor but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0107E: The compensation service is unable to start the compensation process for the executor {0} due to the following exception: {1}
- Explanation: An attempt was made to start the compensation processing for a compensation sphere but an exeception was thrown.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0108E: Compensation is unable to delete the executor with primary key: {0} after compensation due to the following exception: {1}.
- Explanation: An attempt was made to delete the executor after compensation has completed. However the compensation service was unable delete the executor due to an exception.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0109E: Post migration cleanup of 50x coordinators in state {0} failed due to the error {1}
- Explanation: The compensation migration client could not remove 50x coordinators in the {0} state
- User Action: Contact IBM support
- CWWBC0110E: Post migration cleanup of 50x executors in state {0} failed due to the error {1}
- Explanation: The compensation migration client could not remove 50x executors in the {0} state
- User Action: Contact IBM support
- CWWBC0111E: The compenstion action has failed due to the following exception: {0}
- Explanation: The compensation action has been called to compensate but an exception was thrown.
- User Action: Investigate the cause of the exception. Once the cause has been resolved use the Process Choreographer Web Client toeither instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0112E: Compensation action ''{0}'' was invoked, but the action generated a fault: {1}.
- Explanation: Compensation invoked the named compensation action, but that action returned a fault.
- User Action: Investigate the cause of the fault. Once the cause has been resolved use the Process Choreographer Web Client to either instruct the compensation sphere toretry the affected piece of compensation work or to skip the affected piece ofcompensation work. If the cause of the error was not a user error, contact IBM Support.
- CWWBC0113E: The compensation service does not supported nesting of interruptible process: {0} in an uninterruptible process: {1}.
- Explanation: The compensation service has detected that a interruptible process is nested within an uninterruptible process, this tpye of nesting is unsupported.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0114E: Compensation is unable to communicate with the coordinator due to {0}.
- Explanation: An attempt was made to communicate with the coordinator for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0115E: The proclet with index {0} is already finished and cannot be replaced.
- Explanation: An attempt was made to replace an unfinished proclet. However for that proclet has finished and so cannnot bereplaced.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0116E: Compensation is unable to communicate with the contextual proclet that was put into indoubt due to {0}.
- Explanation: An attempt was made to communicate with the contextual proclet that is indoubt for this compensation sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0117E: Compensation is unable to put the sphere into indoubt due to {0}.
- Explanation: An attempt was made to put the sphere into indoubt, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0118E: Compensation is unable to create the coordinator to put the sphere into indoubt due to {0}.
- Explanation: An attempt was made to create the coordiantor to put the sphere into indoubt, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0119E: Compensation is unable to register the proclet : {0} for an indoubt sphere due to {1}.
- Explanation: An attempt was made to register a proclet for an indoubt sphere, but an exception occured.
- User Action: If the cause of the error was not a user error, contact IBM Support.
- CWWBC0120E: No CScopes Compensator has been set up for a work object of the type: {0}
- Explanation: An attempt was made to run a work object of the type: {0}, however, the object hasnot been constructed with a CScopes Compensator and so execution of the work object cannot continue.
- User Action: Contact IBM support.