WebSphere Process Server messages     Operating Systems: All supported
CWZMU0012E: The mediation flow resource associated with component {0} cannot be loaded.
Explanation: The mediation flow resource that this component refers to no longer exists or is corrupt.
User Action: In the assembly editor, right-click, the specified mediation component and select Regenerate Implementation.

 

CWZMU0013W: The {0} input node is not connected.
Explanation:
User Action: Double-click the warning message. In the assembly editor, begin the mediation flow by connecting the input node to a mediation primitive, a callout node, or an input response node.

 

CWZMU0016E: The message types of the {0} source and the {1} target terminals, which are on the wire from the {2} to the {3} mediation primitives, are not compatible.
Explanation:
User Action: Double-click the error message. In the mediation flow editor, delete the wire with the error and insert a new transform between the source and target mediation primitives. In the new transform, create a map between the two message types.

 

CWZMU0018E: The {0} mediation flow contains a loop from an output terminal to the input terminal of an upstream mediation primitive or node.
Explanation: This type of looping connection is not supported at run time.
User Action: Double-click the error message. The node with the looping connection is selected. Remove the looping connection.

 

CWZMU0019E: The {0} primitive name is already being used.
Explanation: In a mediation flow, primitive names must be unique.
User Action: Double-click the error message. The mediation primitive with the duplicate name is selected. Delete one of the duplicate mediation primitives and re-create it with a unique name.

 

CWZMU0020W: The {1} value of the {2} property is not valid for the {0} mediation primitive or node.
Explanation: The value of the property does not match the property type. For example, a Boolean property cannot have a value of 5.
User Action: Change the value or type of the property so that they match.

 

CWZMU0021E: The {0} custom mediation primitive is missing an implementation.
Explanation:
User Action: Double-click the error message. In the Properties view, on the Details tab, select its implementation type and define the implementation.

 

CWZMU0023E: The {0} property of the {1} mediation primitive is missing.
Explanation:
User Action: Double-click the error message. In the Properties view, on the Details tab, specify this property for the mediation primitive.

 

CWZMU0024W: The {1} XSL file for {0} does not match the module content.
Explanation: The module contents changed since the XSL was generated.
User Action: In the Projects menu, select Clean to regenrate the XSL.

 

CWZMU0029E: The {0} mapping file specified for the {1} mediation primitive cannot be found.
Explanation: The mapping file for the mediation primitive is missing, its name misspelled, or is not valid.
User Action: Double-click the error message. The mediation primitive is selected. In the Properties view, on the Details tab, select an existing mapping file or create one.

 

CWZMU0030E: The {0} XSL stylesheet file specified for the {1} XSLT node cannot be found.
Explanation: File has been deleted, moved, renamed.
User Action: Double-click the error message. The XSLT mediation primitive is selected. In the Properties view, on the Details tab, select an XSL file or in the Project menu, select Clean to regenerate the XSL file.

 

CWZMU0031W: The value {0} is not valid for the type {1} on the {2} primitive.
Explanation: The value or type supplied are inconsistent.
User Action: Double-click the error message. The primitive is selected. In the Properties view, on the Details tab, correct the value or the type.

 

CWZMU0032W: The {0} output terminal on the {1} primitive cannot run.
Explanation: The output terminal on the specified node has no corresponding pattern defined.
User Action: Double-click the error message. The specified primitive is selected. In the Properties view, on the Details tab, click Add and define a pattern and specify a terminal.

 

CWZMU0033W: The {0} event emitter has the same event label as the {1} event emitter, but the configurations are different.
Explanation: Event emitters can have the same event label only if they have identical configurations.
User Action: Modify one of the specified event labels to make it unique..

 

CWZMU0034E: The message types on the input and output terminals of the {0} primitive do not match.
Explanation: This primitive does not change the message type.
User Action: Double-click the error message. The specified primitive is selected. In the Properties view, on the Terminal tab, select the output terminal and change the message type to match the message type on the input terminal. Alternatively, select the input terminal and change the message type to match the message type on the output terminal.

 

CWZMU0035W: A direct connection exists from the mediation input to output.
Explanation: In cases of direct connection from mediation input to output, no mediation is performed. The input message to the mediation flow is unchanged.
User Action: If you want mediation, double-click the warning message to add mediation primitives to the flow, and then connect the mediation flow.

 

CWZMU0036E: In the {2} mediation flow, the {0} FanOut primitive that corresponds with the {1} FanIn primitive is missing.
Explanation:
User Action: Double-click the error message. The FanOut primitive is selected. In the mediation flow editor, delete the FanIn primitive and create another one, choosing an existing FanOut primitive or creating another FanOut primitive.

 

CWZMU0037E: No path exists in the flow between the {0} FanOut primitive and the {1} FanIn primitive.
Explanation: A mediation flow path must connect a FanOut primitive and a FanIn primitive.
User Action: Double-click the error message. The FanOut primitive is selected. In the mediation flow editor, create the path between the FanOut and FanIn primitives

 

CWZMU0038E: The {0} mediation component in the mediation flow cannot be resolved.
Explanation:
User Action: In the assembly editor, right-click the specified mediation component and select Regenerate Implementation.

 

CWZMU0039E: The {0} primitive has more than one type assertion for the {1} message element.
Explanation: Only one type can be asserted for a message element.
User Action: Double-click the error message. The primitive is selected. In the Properties view, on the Details tab, remove one of the duplicate entries.

 

CWZMU0040W: The message type of the {0} terminal called {1} of the {2} mediation primitive is not set.
Explanation: If the message type is not set on a wired terminal, then errors might occur in the mediation flow.
User Action: Double-click the warning message. The mediation primitive is selected. In the Properties view, on the Terminal tab, set the message type for the mediation primitive

 

CWZMU0041E: The {0} FanOut primitive does not specify an XPath expression.
Explanation: The XPath expression is required when the FanOut primitive is used in iterate mode.
User Action: Double-click the error message. The FanOut primitive is selected. In the Properties view, on the Details tab, specify an XPath expression for the FanOut primitive.

 

CWZMU0042E: The message type of the {0} terminal called {1} of the {2} XSLT primitive is not set.
Explanation: If the message type is not set on the terminals of an XSLT primitive, then errors might occur in the mediation flow.
User Action: Double-click the error message. The mediation primitive is selected. In the Properties view, on the Terminal tab, set the message type for the XSLT primitive.

 

CWZMU0043E: The {1} reference for the {0} Service Invoke primitive is not defined on the mediation flow component.
Explanation: The specified reference for the Service Invoke primitive must also be defined on the mediation flow component so that the reference can be invoked.
User Action: Double-click the error message. The Service Invoke primitive is selected. In the mediation flow editor, right-click the specified reference and select Rename.

 

CWZMU0044E: The fail terminal of the {0} callout response primitive is not connected.
Explanation: If an unmodeled fault message is received by the callout response primitive, then the unconnected fail terminal will fire.
User Action: Double-click the error message. The callout response primitive is selected. In the mediation flow editor, connect the fail terminal to another primitive.

 

CWZMU0045E: The {0} type on the {1} terminal of the {2} primitive does not match the {3} type that is used for the {4} in the {5} map.
Explanation: A flow fails if the map refers to elements that are not in the input message, or the flow produces output that is does not match the expected content in the service message object.
User Action: Double-click the error message. The primitive is selected. In the mediation flow editor, select the terminal of the primitive and update the terminal type or redefine the map.

 

CWZMU0046E: The {0} type on the {1} terminal of the {2} primitive does not match the empty type that is used for the {3} in the {4} map.
Explanation: A flow fails if the map refers to elements that are not present in the input message, or the flow produces output that is inconsistent with the expected content in the service message object.
User Action: Double-click the error message. The primitive is selected. In the mediation flow editor, select the terminal of the primitive, and update the terminal type or redefine the map.

 

CWZMU0047E: The type {0} used in the {1} primitive is invalid or cannot be found.
Explanation: If a specified type cannot be found, then errors might occur in the mediation flow.
User Action: Double-click the error message. The primitive is selected. In the Properties view, on the Details tab, correct the type.

 

CWZMU0048E: The terminal {0} specified in the {1} primitive is invalid or cannot be found.
Explanation: If a specified terminal cannot be found, then errors might occur in the mediation flow.
User Action: Double-click the error message. The primitive is selected. In the Properties view, on the Details tab, correct the terminal.

 

CWZMU0049E: The terminal {0} is used more than once in the {1} Type Filter primitive.
Explanation: Terminals may only be used once in Type Filter primitives. Firing the same terminal for different type matches may cause errors in the mediation flow.
User Action: Double-click the error message. The primitive is selected. In the Properties view, on the Details tab, ensure each terminal is used only once.

 

CWZMU0050E: The {0} subflow specified for the {1} subflow primitive cannot be found.
Explanation: The subflow file for the subflow mediation primitive is missing, its name misspelled, or is not valid.
User Action: Double-click the error message. The subflow mediation primitive is selected. In the Properties view, on the Details tab, select an existing subflow file or create one.

 

CWZMU0051E: The {0} subflow primitive has no input terminals.
Explanation: A subflow primitive must have at least one input terminal.
User Action: Delete and re-create the subflow primitive.

 

CWZMU0052E: The {0} subflow primitive has no output terminals.
Explanation: A subflow primitive must have at least one output terminal.
User Action: Delete and re-create the subflow primitive.

 

CWZMU0053E: The {0} subflow primitive has no fail terminal.
Explanation: A subflow primitive must have a fail terminal.
User Action: Delete and re-create the subflow primitive.

 

CWZMU0054E: The Version property value {0} in the {1} Endpoint Lookup primitive is of an invalid format.
Explanation: When the Match Policy property is set to ''latest compatible'', the value of the Version property must be of format V.R.M where V, R and M are integers or the wildcard * character.
User Action: Double-click the error message. The Endpoint Lookup mediation primitive is selected. In the Properties view, on the Details tab, change the value of the Version property so that it has the correct format.

 

CWZMU0055W: The {0} subflow primitive does not have a value set for the reference {1}.
Explanation: A reference defined on the subflow has not been mapped to a reference in the flow containing the subflow mediation primitive.
User Action: Double-click the error message. The subflow mediation primitive is selected. In the Properties view, on the References tab, select a value for the given reference.

 

CWZMU0056E: The {0} subflow primitive has the invalid value {1} for the reference {2}.
Explanation: A reference defined on the subflow has been mapped to a reference that does not exist in the flow containing the subflow mediation primitive.
User Action: Double-click the error message. The subflow mediation primitive is selected. In the Properties view, on the References tab, select a valid value for the given reference.

 

CWZMU0057E: The type {0} cannot be set at {1} in the {2} primitive.
Explanation: The specified type cannot be asserted at the specified XPath due to type incompatibilities.
User Action: Double-click the error message. The asserting primitive is selected. In the Properties view, on the Details tab, correct the value of the XPath or Type properties.

 

CWZMU0058E: A deadlock will occur when the mediation flow performs a service invocation using the {0} node in the {1} mediation flow due to the combination of transactional and asynchronous settings
Explanation: When the mediation flow transaction qualifier is Global, the Asynchronous Invocation qualifier for the reference is set to Commit, and the operation is request-response, a deadlock will occur if the callout node or service invoke mediation primitive attempts to make an asynchronous invocation using the deferred response invocation style
User Action: Double-click the error message. The mediation primitive or callout node is selected. Change the invocation style property of the mediation primitive or callout node, or change the transaction qualifier of the mediation flow component, or change the asynchronous qualifier of the component reference

 

CWZMU0059E: A deadlock will occur when the mediation flow performs a service invocation using the {0} primitive called from the {1} subflow in the {2} mediation flow due to the combination of transactional and asynchronous settings
Explanation: When the mediation flow transaction qualifier is Global, the Asynchronous Invocation qualifier for the reference is set to Commit, and the operation is request-response, a deadlock will occur if the callout node or service invoke mediation primitive attempts to make an asynchronous invocation using the deferred response invocation style
User Action: Double-click the error message. The mediation primitive or callout node is selected. Change the invocation style property of the mediation primitive or callout node, or change the transaction qualifier of the mediation flow component, or change the asynchronous qualifier of the component reference

 

CWZMU0060W: A deadlock may occur when the mediation flow performs a service invocation using the {0} node in the {1} mediation flow due to the combination of transactional and asynchronous settings
Explanation: When the mediation flow transaction qualifier is Global, the Asynchronous Invocation qualifier for the reference is set to Commit, and the operation is request-response, a deadlock will occur if the callout node or service invoke mediation primitive attempts to make an asynchronous invocation using the deferred response invocation style
User Action: Double-click the error message. The mediation primitive or callout node is selected. Change the invocation style property of the mediation primitive or callout node, or change the transaction qualifier of the mediation flow component, or change the asynchronous qualifier of the component reference

 

CWZMU0061W: A deadlock may occur when the mediation flow performs a service invocation using the {0} primitive called from the {1} subflow in the {2} mediation flow due to the combination of transactional and asynchronous settings
Explanation: When the mediation flow transaction qualifier is Global, the Asynchronous Invocation qualifier for the reference is set to Commit, and the operation is request-response, a deadlock will occur if the callout node or service invoke mediation primitive attempts to make an asynchronous invocation using the deferred response invocation style
User Action: Double-click the error message. The mediation primitive or callout node is selected. Change the invocation style property of the mediation primitive or callout node, or change the transaction qualifier of the mediation flow component, or change the asynchronous qualifier of the component reference

 

CWZMU0062E: The {0} data handler configuration specified for the {1} data handler primitive cannot be found.
Explanation: The data handler configuration for the data handler mediation primitive is missing, its name misspelled, or is not valid.
User Action: Double-click the error message. The data handler mediation primitive is selected. In the Properties view, on the Details tab, select an existing data handler configuration or create one.

 

CWZMU0111W: Mediation Module "{0}" contains 2 or more Mediation Flows.
Explanation: A mediation module can contain no more than 1 mediation flow.
User Action: Place additional mediation flows in separate modules.

 

CWZMU0210E: Cannot run SCDL MFC Validator runnable.
Explanation:
User Action:

 

CWZMU0211E: The sca.module resource could not load.
Explanation: The sca.module does not exist, is corrupted, or contains incorrect data.
User Action: In the Project menu, right-click the sca.module resource and select Clean > Clean all projects.

 

CWZMU0212E: The mediation flow implementation for the {0} mediation component cannot be found.
Explanation: The mediation flow implementation does not exist, is corrupted, or contains incorrect data.
User Action: In the assembly editor, right-click the specified mediation component and select Regenerate Implementation.

 

CWZMU0213E: The {0} interface on the {1} mediation component is not a Web Services Description Language (WSDL) interface.
Explanation: The specified interface is a Java interface, but the mediation component is not a Java component. Only Java components can have Java interfaces.
User Action: In the assembly editor, select the specified mediation component. In the Properties view, on the Details tab, right-click Interfaces, select Add Interface, and choose a WSDL interface.

 

CWZMU0214E: The {0} mediation component contains an interface ({1}) that does not match a corresponding interface in the mediation flow implementation.
Explanation:
User Action: In the assembly editor, right-click the specified mediation component and select Synchronize Interfaces and References > to Implementation.

 

CWZMU0215E: The {0} reference on the {1} mediation component is not a Web Services Description Language (WSDL) interface.
Explanation: The reference is a Java reference and only Java components can have Java reference.
User Action: In the assembly editor, select the specified mediation component. In the Properties view, on the Details tab, right-click References, select Add Reference, and choose a WSDL reference.

 

CWZMU0216E: The {0} mediation component contains a reference that is either missing an interface or has more than one interface.
Explanation: Each reference must contain only one interface.
User Action: Set up an interface if it is missing from the reference. If the reference has more than one interface, in the Physical Resources view, open the component file for the specified mediation and correct the content of the reference element so that it includes only one interface element.

 

CWZMU0217E: The {0} mediation component contains a reference ({1}) that does not match a corresponding reference in the mediation flow implementation.
Explanation:
User Action: In the assembly editor, right-click the specified mediation component and select Synchronize Interfaces and References > to Implementation.

 

CWZMU0218E: The {0} mediation flow implementation contains a reference ({1}) that does not match a corresponding reference in the mediation component.
Explanation:
User Action: In the assembly editor, right-click the specified mediation component and select Synchronize Interfaces and References > from Implementation.

 

CWZMU0219E: The {0} mediation component contains a reference ({1}) that does not match the corresponding reference in the mediation flow implementation.
Explanation:
User Action: Action: In the assembly editor, right-click the specified mediation component and select Synchronize Interfaces and References > from Implementation or Synchronize Interfaces and References > to Implementation, depending on which reference contains the required interface.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009