- CWSXM0054E: Key {0} not found in context store when locating correlation information for module {1}
- Explanation: The key identifies the correlation information for the reply message. The key may be absent if a reply has already been received with the same ticket, or if the corresponding message has been deleted from the modules correlation destination
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM0055E: Key {0} is already present in the context store when storing correlation information for module {1}
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM0100E: Multiple replies have been produced for a single request flow in module {0}
- Explanation: A mediation request flow has invoked multiple request/reply services, and nore than one of the responses have produced reply messages from the response flows. Alternatively the request or response flow has produced more than one result or fault.
- User Action: Ensure that either the request flow is limited to making a single request/reply invocation or result or fault, or that only one response flow produces a reply.
- CWSXM0101E: A mediation response or fault flow attempted to invoke a service in module {0}
- Explanation: Mediation response and fault flows are not permitted to invoke services.
- User Action: Ensure that the response and fault flows in the module do not invoke services.
- CWSXM0102E: The operation {0} cannot be resolved.
- Explanation: The named operation cannot be found for the reference that is invoked by the mediation flow.
- User Action: Ensure that the operation name that is used in the mediation flow is correct.
- CWSXM0103E: Could not locate the EJB session bean for component {0} in module {1}
- Explanation: The requested EJB session bean could not be located.
- User Action: Check the deployment of the mediation flow component.
- CWSXM0104E: A runtime error occured when saving context for a mediation flow in mediation component {0} in module {1}
- Explanation: An internal error occured when saving the context information used by a mediation flow for the given component.
- User Action: Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
- CWSXM0105E: A runtime error occured when saving context for a mediation flow in mediation component {0} in module {1}
- Explanation: An error occured when saving the context information used by a mediation flow for the given component.
- User Action: Check the causal exception for more information.
- CWSXM0106E: A runtime error occured when receiving a response for mediation component {0} in module {1}
- Explanation: An internal error occured when the mediation flow component processed a response message.
- User Action: Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
- CWSXM0107E: A runtime error occured when receiving a response for mediation component {0} in module {1}
- Explanation: An internal error occured when the mediation flow component processed a response message.
- User Action: Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
- CWSXM0108E: A runtime error occured when creating an outbound message in mediation component {0} and module {1}
- Explanation: An internal error occured when the mediation flow component was creating an outbound message.
- User Action: Check the validity and correct deployment of the mediation flow component and the validity of references that are invoked.
- CWSXM0109E: Multiple connections to reference {0} in mediation component {1} and module {2}
- Explanation: The reference is connected to multiple services but only a single service can be connected to on a reference in a mediation flow.
- User Action: Check the validity of the mediation flow and the validity of references that are invoked.
- CWSXM0110E: Service runtime exception invoking a Java component implementing a custom primitive in mediation component {0} in module {1}: {2}
- Explanation: An exception occurred when invoking the Java component implementing a custom primitive. Check the causal exception information for more detail.
- User Action: Check the validity of the deployed custom mediation component.
- CWSXM0111E: Service runtime exception invoking an import from mediation component {0} in module {1}: {2}
- Explanation: An exception occurred when invoking an import from the mediation flow. Check the causal exception information for more detail.
- User Action: Check the availability of the service referred to by the import.
- CWSXM0112E: Dynamic endpoint selection is disabled and there are no wired connections to reference {0} in mediation component {1} and module {2}
- Explanation: The reference is not connected to any import and use of dynamic endpoint address selection is disabled.
- User Action: Check the validity of the mediation flow and the validity of references that are invoked.
- CWSXM0113E: No wired connections to reference {0} and the service message object does not contain an endpoint address.
- Explanation: The reference is not connected to any import and a dynamic endpoint address was not provided in the service message object.
- User Action: Check the validity of the mediation flow and the validity of references that are invoked.
- CWSXM0114E: The dynamic endpoint {0} specified in the service message object was not found when invoking reference {1}
- Explanation: The dynamic endpoint address specified in the service message object was not found.
- User Action: Check the validity of the mediation flow and the source of the dynamic endpoint stored in the service message object.
- CWSXM0200E: Could not locate the mediation flow for component {0} in module {1}
- Explanation: The requested mediation flow session bean could not be located.
- User Action: Check the deployment of the mediation flow component.
- CWSXM0201E: Exception returned by mediation flow for component {0} in module {1}
- Explanation: The mediation flow returned an exception that was not handled by the mediation flow. An exception may be returned if the mediation primitive does not define a failure terminal, or the failure terminal is not wired.
- User Action: Check the mediation flow to ensure that all failure terminals on primitives are wired.
- CWSXM0202E: An unexpected exception occurred when processing mediation flow for component {0} in module {1}
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM0203E: An unexpected exception occurred when accessing the persistent store for component {0} in module {1}
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM0204E: A configuration error occurred when invoking a mediation flow.
- Explanation: The mediation flow returned a configuration exception when invoked. The exception may indicate that a primitive in the flow failed to obtain a required resource.
- User Action: Check the underlying exception for more details of the cause of the configuration error.
- CWSXM0205E: An unexpected business logic exception occurred.
- Explanation: The mediation flow returned an exception that indicated that a business logic error occurred.
- User Action: Check the underlying exception for details of the business logic error.
- CWSXM0206E: An unexpected exception occurred.
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM1000E: Could not locate runtime mediation flow for mediation component {0} in module {1}
- Explanation: No runtime mediation flow definitions were found for the mediation component.
- User Action: Check the mediation component has a mediation flow defined and check for any earlier exceptions in loading the definition.
- CWSXM1001E: No request flow found for operation {0} on port type {1}. In mediation component {2} in module {3}
- Explanation: The request flow for the operation could not be found by the flow engine. This could be because no request flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
- User Action: Verify that the mediation component has a request flow defined for the operation.
- CWSXM1002E: No response flow found for operation {0} on reference {1}. In mediation component {2} in module {3}
- Explanation: The response flow for the operation invoked on the reference could not be found by the flow engine. This could be because no response flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
- User Action: Verify that the mediation component has a response flow defined for the operation and check for any earlier exceptions in loading the response flow.
- CWSXM1003E: No response fault flow found for fault message {0} from operation {1} on reference {2}. In mediation component {3} in module {4}
- Explanation: The response flow for the operation invoked on the reference could not be found by the flow engine. This could be because no response flow is defined for this operation in the mediation component, or because of an earlier problem in loading the mediation flow.
- User Action: Verify that the mediation component has a response fault flow defined for the fault message and operation and check for any earlier exceptions in loading the response fault flow.
- CWSXM1004E: An invalid input is specified for a flow. In mediation component {0} in module {1}
- Explanation: The flow has an invalid or unknown input.
- User Action: Validate the mediation flow definition.
- CWSXM1005E: Error whilst instantiating mediation primitive {0}. In mediation component {1} in module {2}
- Explanation: The mediation primitive could not be instantiated.
- User Action: Validate the mediation flow definition, and check the causal exception for more information.
- CWSXM1006E: Error whilst setting properties of mediation primitive {0}. In mediation component {1} in module {2}
- Explanation: An error occured whilst trying to set the properties of the mediation primitive.
- User Action: Verify that the correct properties are defined for the mediation primitive in the mediation flow definition, and check the causal exception for more information.
- CWSXM1007E: Mediation primitive {0} failed to initialize. In mediation component {1} in module {2}
- Explanation: During the primitives initialization, the named mediation primitive encountered an error.
- User Action: Verify that the configuration of the mediation primitive in the mediation flow definition, and check the causal exception for more information.
- CWSXM1008E: Key of type {0} is not of expected type.
- Explanation: The key class is not of the expected type for this flow engine.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM1009E: Could not locate the runtime mediation flow for mediation component {0} in module {1}
- Explanation: There was a problem in locating the runtime instance of the mediation flow.
- User Action: Check the causal exception for more information.
- CWSXM1010E: Could not locate the runtime mediation flow for mediation component {0} in module {1}
- Explanation: There was a problem in locating the runtime instance of the mediation flow.
- User Action: Check the causal exception for more information, and validate that the SCA module started with no errors.
- CWSXM1011E: A runtime error occured invoking the request flow for operation {0}, on port type {1}. In mediation component {2} in module {3}
- Explanation: An internal error occured when invoking the request flow for the operation.
- User Action: Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
- CWSXM1012E: A runtime error occured invoking the response flow for operation {0} on reference {1}. In mediation component {2} in module {3}
- Explanation: An internal error occured when invoking the response flow for the operation on the named reference.
- User Action: Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
- CWSXM1013E: A runtime error occured invoking the response fault flow for fault message {0} and operation {1} on reference {2}. In mediation component {3} in module {4}
- Explanation: An internal error occured when invoking the fault response flow for the fault message and operation on the named reference.
- User Action: Check the validity and correct deployment of the mediation flow component, and check the causal exception for more information.
- CWSXM1016E: The reference {0} for custom mediation {1} is undefined.
- Explanation: The reference for the custom mediation is not defined on the mediation component.
- User Action: Check the validity and correct deployment of the mediation component.
- CWSXM1017E: Request flow runtime instance is unavailable.
- Explanation: The request flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
- User Action: Check the validity of the mediation flow component, and check for previous errors.
- CWSXM1018E: Response flow runtime instance is unavailable.
- Explanation: The response flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
- User Action: Check the validity of the mediation flow component, and check for previous errors.
- CWSXM1019E: Response fault flow runtime instance is unavailable.
- Explanation: The response fault flow runtime instance could not be found. This could be because of a previous problem in creating the runtime flow.
- User Action: Check the validity of the mediation flow component, and check for previous errors.
- CWSXM1020E: An unknown exception occured during the processing of mediation primitive {0}: {1}
- Explanation: An unknown exception occurred during the processing of the specified mediation primitive or custom mediation.
- User Action: Check the causal exception for more information.
- CWSXM1021E: No input terminal named {0} defined for mediation primitive {1}
- Explanation: A mediation primitive attempted to obtain an input terminal which does not exist.
- User Action: Check the validity of the mediation flow component.
- CWSXM1022E: No output terminal named {0} defined for mediation primitive {1}
- Explanation: A mediation primitive attempted to obtain an output terminal which does not exist.
- User Action: Check the validity of the mediation flow.
- CWSXM1023E: Exception when invoking flow action: {0}
- Explanation: An error occurred when the action of a flow was invoked.
- User Action: Check the causal exception for more information.
- CWSXM1024E: The reference {0} for callout {1} is undefined.
- Explanation: The reference for the callout is not defined on the mediation component.
- User Action: Check the validity and correct deployment of the mediation component.
- CWSXM1025E: An unexpected exception occurred during flow invocation: {0}
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM1026E: Null is an invalid argument for a datasource JNDI name.
- Explanation: A mediation primitive tried to locate a datasource with a null JNDI name.
- User Action: Ensure that the JNDI name is valid.
- CWSXM1027E: An exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''
- Explanation: The datasource with the JNDI name ''{0}'' could not be located. The causal exception if available will contain more information.
- User Action: Ensure that the JNDI service is available and an appropriate datasource has been configured.
- CWSXM1028E: A class cast exception occurred when attempting to obtain a datasource from JNDI with the name ''{0}''
- Explanation: The object with the JNDI name ''{0}'' was not of type DataSource. The causal exception if available will contain more information.
- User Action: Ensure that the object bound into JNDI is a DataSource.
- CWSXM1032E: Reference {0} for custom mediation {1} does not define an operation named {2}
- Explanation: There is no operation of the specified name defined on the reference for the custom mediation.
- User Action: Check the configuration of the custom mediation.
- CWSXM1033E: Reference {0} for custom mediation {1} defines a one way interface.
- Explanation: Custom mediations may only define a two-way interface.
- User Action: Check the configuration of the custom mediation.
- CWSXM1034E: Mediation primitive {0} in mediation flow {1} failed to initialize.
- Explanation: The mediation primitive threw an exception during its initialization meaning the flow will be unavailable.
- User Action: Check the configuration of the mediation primitive, and the value of any module properties it uses. Also check FFDC for any exceptions generated by the primitive.
- CWSXM1035E: Mediation flow {0} in mediation component {1} in module {2} could not be build and will be unavailable.
- Explanation: An exception occurred during the building of the mediation flow which will render it unavailable for invocation.
- User Action: Check FFDC for any exceptions arising from the building of the flow, and check the flow configuration and values of any module properties used within the flow.
- CWSXM1036E: Custom mediation {0} contains an invalid root property value of {1}
- Explanation: The root property of the custom mediation is invalid. It must be either ''/'' or ''/body''
- User Action: Modify the root property within the tooling to be either ''/'' or ''/body''
- CWSXM1037E: Custom mediation {0} does not specify a root property value
- Explanation: The root property of the custom mediation is not specified.
- User Action: Set the root property for the custom mediation in the tooling.
- CWSXM2003E: The contents of ''{0}'' in the ServiceMessageObject did not meet their constraints.
- Explanation: During validation of a ServiceMessageObject, the contents of the message were found to be inconsistent with constraints. For example, a value might be out of bounds, or a required attribute might be unset.
- User Action: Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect. You may be able to disable message validation in order to ignore this condition.
- CWSXM2004E: The ServiceMessageObject body was not of expected type {0}
- Explanation: The body of a ServiceMessageObject was not of the expected type. This message usually refers to SMO validation in a mediation primitive, which compares the SMO to a type specified on one of the primitive''s terminals.
- User Action: Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect, or correct the expected type.
- CWSXM2005E: The ServiceMessageObject body was not set.
- Explanation: A ServiceMessageObject was found to have no body, but validation required the SMO body to be set.
- User Action: Inspect the origin of the ServiceMessageObject to see where the message might have become incorrect.
- CWSXM2006E: Malformed QName: ''{0}''
- Explanation: The system encountered an expanded QName which was not of correct format
- User Action: If the malformed QName is contained within a user message, then determine why the message contains a badly formatted QName.
- CWSXM2007E: Error: multiple type or message definitions for {0}
- Explanation: There is a WSDL Message definition with the same name (namespace and local part) as an XSD type definition.
- User Action: Alter either the WSDL or the XSD definitions so that multiple objects do not share the same name.
- CWSXM3000E: {0} is not a valid value for property ''{1}''
- Explanation: A setter method on a mediation primitive has been called with a value which is not allowed. Usually this means that the mediation configuration is not correct.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3001E: Property ''{0}'' is not set.
- Explanation: The mediation primitives configuration is missing a required property. Usually this means that the mediation configuration is not correct.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3002E: MediationServices object not set.
- Explanation: The mediation primitives configuration was incomplete.
- User Action: Ensure that the configuration of the mediation primitive and mediation flow is valid.
- CWSXM3003E: Input message is null.
- Explanation: A mediation primitive was invoked without a message to mediate.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM3004E: Mediation parameter is null for property ''{0}''
- Explanation: A null value is not valid for the named property.
- User Action: A setter method on a mediation primitive has been called with a null value. This is not allowed. Usually this means that the mediation configuration is not correct.
- CWSXM3005E: SCAServices object not set.
- Explanation: The mediation primitives configuration was incomplete.
- User Action: Ensure that the configuration of the mediation primitive and mediation flow is valid.
- CWSXM3006E: RuntimeServices object not set.
- Explanation: The mediation primitives configuration was incomplete.
- User Action: Ensure that the configuration of the mediation primitive and mediation flow is valid.
- CWSXM3007E: The mediation primitive was called with a message which was not a ServiceMessageObject.
- Explanation: The mediation primitive attempted to mediate a message which was not a ServiceMessageObject. This is not allowed.
- User Action: Ensure that the configuration of the mediation flow is valid.
- CWSXM3008W: The StockQuote sample released with v6.0 of this product is now deprecated. Please upgrade the StockQuote sample, and any projects based upon it, to the version shipped with v6.0.1.1 or later.
- Explanation: The v6.0 StockQuote sample is deprecated, and should be replaced with later versions of the sample. The v6.0 sample is unlikely to work with future versions of the runtime. User-created Mediation Modules are not affected.
- User Action: Upgrade the version of the StockQuote sample. If this message is issued while running a user Mediation Module which was based on the StockQuote sample, it may be necessary to reconstruct the user application based on the updated version of the sample.
- CWSXM3100E: Root property evaluated to null.
- Explanation: The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. This suggests that the value is not set.
- User Action: Ensure that the configuration of the Root property is set to a valid value.
- CWSXM3101E: Root property evaluated to multiple elements which is not allowed.
- Explanation: The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. However, in the message being mediated, it evaluated to multiple elements.
- User Action: Correct the Root property.
- CWSXM3102E: Root property evaluated to a {0}
- Explanation: The Root property on XSLTransform mediation primitive must evaluate to a single DataObject. It must not evaluate to a collection of DataObjects or to a value other than a single DataObject.
- User Action: Correct the Root property.
- CWSXM3103E: Exception while evaluating the Root property.
- Explanation: An Exception was caught while XSLTransform was evaluating the Root, prior to transformation.
- User Action: Use the nested Exception to diagnose the problem.
- CWSXM3104E: Exception while generating XML prior to transformation.
- Explanation: The DataObject identified by the Root property could not be serialized as XML, prior to XSL transformation.
- User Action: Use the nested Exception to diagnose the problem.
- CWSXM3105E: Exception during transformation.
- Explanation: An Exception occurred during XSL transformation.
- User Action: Use the nested Exception to diagnose the problem.
- CWSXM3106E: Exception while parsing transformed XML: {0}
- Explanation: The XSL transformation completed successfully, but the resultant XML could not be converted into a DataObject.
- User Action: Use the nested Exception to diagnose the problem.
- CWSXM3107E: Exception while setting the transformed DataObject back into the root location.
- Explanation: The XSL transformation completed successfully, but the transformed DataObject could not be set into the root position in the ServiceMessageObject.
- User Action: Use the nested Exception to diagnose the problem.
- CWSXM3108E: XSLTransform could not find or load the stylesheet ''{0}''
- Explanation: The XSLTransform property named the given file, which was not found at runtime.
- User Action: Correct the XSLTransform property, or make the stylesheet available.
- CWSXM3109E: Unexpected Exception while initializing the XSL transformation engine.
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM3110E: Exception while initializing the XSL transformation engine with stylesheet ''{0}''
- Explanation: An Exception was caught while initializing the XSL transformation engine. This usually indicates a syntax or other error relating to the source stylesheet.
- User Action: Inspect the nested exception to diagnose the problem.
- CWSXM3111E: XSL transformation file not specified for {0}
- Explanation: The mediation primitives configuration does not specify the XSL transformation file to use.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3150E: Unable to connect to the database using datasource ''{0}''. Refer to the nested exception for more information.
- Explanation: Unable to obtain a connection to the database. The nested exception, if available, will contain more information.
- User Action: Ensure that the database is available for connection and any authentication settings have been configured.
- CWSXM3151E: Database schema is invalid for the ''{0}'' primitive.
- Explanation: The database schema is invalid for the named primitive.
- User Action: Ensure that the database schema conforms to the IBM supplied schema. Please refer to the documentation to locate the schema.
- CWSXM3152E: Unable to access the database to store the message. This may be due to the database being unavailable, incorrect access rights or invalid database schema. Please refer to the nested exception for more information.
- Explanation: Unable to access the database to store the message. The nested exception, if available, will contain more information.
- User Action: Ensure that the correct access rights have been set, the database is available and the schema conforms to the IBM supplied schema.
- CWSXM3153E: Unable to serialize the message information as an XML document.
- Explanation: Unable to serialize the message information as an XML document. The nested exception, if available, will contain more information.
- User Action: Ensure that the message being mediated is valid.
- CWSXM3154E: Unable to store the message within the configured transaction.
- Explanation: This exception is unexpected. The cause is not immediately known.
- User Action: If the problem persists, see problem determination information on the product support page at http://www.ibm.com/software/integration/wps/support/.
- CWSXM3155E: A problem occurred communicating with the database.
- Explanation: A problem occurred communicating with the database. The nested exception, if available, will contain more information.
- User Action: Ensure that the database is available and configured correctly.
- CWSXM3156E: A problem occurred obtaining the JNDI InitialContext.
- Explanation: A problem occurred obtaining the JNDI InitialContext. The nested exception, if available, will contain more information.
- User Action: Ensure that the JNDI service is available.
- CWSXM3157E: A class cast exception occurred when attempting to obtain a String from JNDI with the name ''{0}''
- Explanation: The object with the JNDI name ''{0}'' was not of type String. The causal exception, if available, will contain more information.
- User Action: Ensure that the object bound into JNDI is a String.
- CWSXM3201E: Unable to locate a key value from ''{0}'' within the message.
- Explanation: An unsuccessful attempt was made to locate a value in the message to be used as a key into the database.
- User Action: Ensure that the message contains a value in the specified location.
- CWSXM3202E: An exception occurred when attempting to lookup the information in the specified database.
- Explanation: An exception occurred when attempting to locate the information in the database. Ensure that the mediation primitive is configured to read only from supported database column types.
- User Action: Check that the database is available and refer to the documentation for supported database column types.
- CWSXM3203E: An exception occurred when communicating with the database.
- Explanation: See the nested exception for more information.
- User Action: Ensure that the database is available and configured correctly.
- CWSXM3204E: More than one row was returned from the database column ''{1}'' using the key ''{0}''
- Explanation: More than one row of data was returned from the database. This is not allowed.
- User Action: Ensure that the database key column only contains unique values.
- CWSXM3205E: Unable to obtain a connection to the database.
- Explanation: Unable to obtain a connection to the database. The nested exception, if available, will contain more information.
- User Action: Ensure that the database is available for connection and any necessary authentication rights have been configured in the appropriate datasource.
- CWSXM3206E: Cannot connect to the database using table {0} with column(s) {1}
- Explanation: An exception occurred when attempting to read from the database. The nested exception, if available, will contain more information.
- User Action: Ensure that the property values have been specified correctly because the more probable cause of this exception is an invalid table or column name.
- CWSXM3207E: Unable to convert the value of type ''{0}'' which was obtained from the database into the specified type ''{1}''
- Explanation: A type mismatch occurred between the type of the value obtained from the database and the type configured in mediation primitive.
- User Action: Ensure the mediation primitive is configured correctly and the type of the value obtained from the database is one of the supported types.
- CWSXM3208E: An exception occurred when attempting to set the value ''{1}'' into the message with a location path of ''{0}''. Ensure that the path specified is a valid location to store the value.
- Explanation: An exception occurred attempting to set value ''{1}'' into the message at location ''{0}''
- User Action: Ensure that the path location is a valid location for the message being mediated.
- CWSXM3209E: Value obtained from the ''{2}'' column using the key ''{1}'' was null and could not be set in the message because it has a type of ''{0}''
- Explanation: A null value was obtained from the database column using the named key. This is not allowed.
- User Action: Ensure that the value contained in the database is compatible with the message element type.
- CWSXM3210E: The value obtained from the message at location ''{0}'' did not return a single element to be used as a key into the database.
- Explanation: The value obtained from the message at the specified location did not return a single element to be used as a key into the database. This is not allowed.
- User Action: Ensure that the location in the message to be used as a key is a single element and not a collection of elements.
- CWSXM3250E: The list of filter expressions contains null in one or more positions.
- Explanation: A MessageFilter primitive configuration contains a null Filter definition. Usually this means that the mediation flow configuration is not correct.
- User Action: Correct the mediation flow configuration.
- CWSXM3251E: The list of filter expressions contains duplicate terminal name ''{0}''
- Explanation: A MessageFilter primitive configuration contains multiple filter expressions with the same terminal name.
- User Action: Correct the mediation primitive configuration, ensuring that terminal names are used only once for a MessageFilter primitive.
- CWSXM3300E: Fail primitive component ''{0}'', module ''{1}'', reference ''{2}'', interface ''{3}'' raised a FailFlowException. The user-supplied error message is ''{4}''
- Explanation: A Fail mediation primitive has raised a FailFlowException.
- User Action: Examine any user-supplied error message.
- CWSXM3401E: Incorrect parameters given. Usage: {0}
- Explanation: The script was called with an incorrect set of parameters.
- User Action: Call the script again with parameters described in the message.
- CWSXM3402E: -createDb cannot be used in a Network Deployment environment.
- Explanation: The "-createDb" option creates an embedded Cloudscape database.
- User Action: See the InfoCenter for instructions on how to install the database in a Network Deployment environment.
- CWSXM3403E: The script cannot be used when multiple servers share one node. There are {0} servers on node {1}.
- Explanation: There is more than one server configured for the node.
- User Action: See the InfoCenter for instructions on how to create data sources for multiple servers.
- CWSXM3404I: Saving configuration.
- Explanation: The configuration changes are being saved.
- User Action: None.
- CWSXM3405I: Data source configuration completed successfully.
- Explanation: The data source configuration changes have been completed.
- User Action: None.
- CWSXM3406I: Data source for {0} already exists.
- Explanation: A data source with the specified JNDI name already exists.
- User Action: None.
- CWSXM3407I: Data source for {0} does not exist.
- Explanation: A data source with the specified JNDI name does not exist.
- User Action: None.
- CWSXM3408I: Database {0} already exists.
- Explanation: A database with the specified location and name already exists.
- User Action: None.
- CWSXM3409I: Database {0} does not exist.
- Explanation: A database with the specified location and name does not exist.
- User Action: None.
- CWSXM3410E: Database {0} already exists.
- Explanation: The script cannot create a database in the named location because a database already exists there.
- User Action: Check whether the database has already been installed correctly. If not, check whether it is safe to delete the database and run this script again.
- CWSXM3411E: The ''ij'' command was not found. The expected location of ''ij'' is "{0}"
- Explanation: The script cannot find the ij.bat or ij.sh command in the named directory. If this file does not exist the server installation is corrupted.
- User Action: Reinstall the application server to repair the installation.
- CWSXM3412I: Creating DDL file {0}
- Explanation: The script is creating the DDL file for the Cloudscape database.
- User Action: None.
- CWSXM3413I: Creating Cloudscape database. See log file for details at {0}
- Explanation: The script is creating a Cloudscape database using the DDL file. The results of the database creation are saved to a log file.
- User Action: None.
- CWSXM3414E: Configuration failed. JDBC provider {0} does not exist.
- Explanation: The script needs this JDBC provider to configure the data source.
- User Action: Restore the named JDBC provider or manually configure the data source.
- CWSXM3415E: Data source for {0} already exists.
- Explanation: A data source with the specified JNDI name already exists.
- User Action: If the data source is already correctly configured, do not configure it again. Otherwise manually configure the data source to avoid naming conflicts with the existing configuration.
- CWSXM3416E: CMP connection factory {0} already exists.
- Explanation: The script cannot continue because the connection factory it would create already exists.
- User Action: If the data source is already correctly configured, do not configure it again. Otherwise manually configure the data source to avoid naming conflicts with the existing configuration.
- CWSXM3417I: Creating data source {0} under JDBC provider {1}
- Explanation: The script is creating a data source for the named JDBC provider.
- User Action: None.
- CWSXM3418I: Configuring data source {0}
- Explanation: The script is creating the data source configuration object.
- User Action: None.
- CWSXM3419I: Creating CMP connection factory for data source {0}
- Explanation: The script is creating a CMP connection factory for the data source.
- User Action: None.
- CWSXM3420I: Successfully removed CMP connection factory {0}
- Explanation: The script has removed the connection factory used by the data source.
- User Action: None.
- CWSXM3421W: Cannot find CMP connection factory {0}
- Explanation: The CMP connection factory associated with the data source was not found.
- User Action: Check whether the CMP connection factory exists and manually remove it.
- CWSXM3422I: Successfully removed data source {0}
- Explanation: The script has removed the data source.
- User Action: None.
- CWSXM3423W: Cannot find data source {0}
- Explanation: The data source was not found.
- User Action: Check whether the data source exists and manually remove it.
- CWSXM3424E: Node name and server name must be specified in a Network Deployment environment.
- Explanation: The script was used in a Network Deployment environment but the node name and server name were not specified on the command line.
- User Action: Call the script again specifying the node name and server name on the command line
- CWSXM3425E: The node name ''{0}'' or server name ''{1}'' are invalid.
- Explanation: The node and server name combination could not be found.
- User Action: Call the script again specifying a valid node name and server name
- CWSXM3426I: Created Cloudscape database successfully.
- Explanation: The script has created a Cloudscape database using the DDL file.
- User Action: None.
- CWSXM3427E: Cloudscape database creation encountered errors. See log file for details at {0}
- Explanation: The script attempted to create a Cloudscape database using the DDL file. The results of the database creation are saved to a log file.
- User Action: Check the log file for problems creating the database.
- CWSXM3428I: The Cloudscape database will not be deleted. If the database is no longer required then it must be removed manually.
- Explanation: The script does not remove the database.
- User Action: If desired, remove the database manually.
- CWSXM3429E: Cannot create the requested dbLocation {0}. {1}
- Explanation: The script cannot write files to the location specified in the -dbLocation parameter
- User Action: If the location exists, check it is a directory, and the script has write access. If the location does not exist, check the script has write access to the parent directory.
- CWSXM3430I: Modifying existing J2C authentication data alias: {0}.
- Explanation: A J2C authentication alias with the required name was found and it is modified with the new username and password.
- User Action: None.
- CWSXM3431I: Creating new J2C authentication data alias: {0}.
- Explanation: A J2C authentication alias with the required name was not found and a new one is created.
- User Action: None.
- CWSXM3432W: Found JDBC provider template {0}, but it might be the wrong one.
- Explanation: A matching JDBC provider template was found but it may not be the correct one.
- User Action: Check the JDBC Provider used for the Data Source and inform the System Administrator if it is the wrong one.
- CWSXM3433E: The JDBC provider cannot be used because a template was not found for it: {0}.
- Explanation: The script could not find a template for the required JDBC provider, so the JDBC provider cannot be used.
- User Action: Report the problem to the System Administrator.
- CWSXM3434I: Using existing JDBC provider: {0}.
- Explanation: The required JDBC provider already exists.
- User Action: None.
- CWSXM3435I: Creating JDBC provider: {0}.
- Explanation: The required JDBC provider does not exist and is being created.
- User Action: None.
- CWSXM3436E: The -userid <userid> and -passwd <passwd> parameters are required for this script.
- Explanation: The username and password parameters are required for this script but one or both of them were empty.
- User Action: Run the script again, specifying values for both the username and password.
- CWSXM3450E: An exception occurred when attempting to set the value ''{1}'' into the message with a location path of ''{0}''. Ensure that the path specified is a valid location to store the value.
- Explanation: An exception occurred attempting to set value ''{1}'' into the message at location ''{0}''
- User Action: Ensure that the path location is a valid location for the message being mediated.
- CWSXM3451E: {0} is not a valid XPath expression for property ''value''
- Explanation: When the property ''type'' is ''copy'', then the value must be an XPath expression describing the location of the source element. The mediation configuration is not correct.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3452E: property ''target'' {0} is an XPath expression that resolves to more than one message element
- Explanation: The target must be a valid XPath expression that resolves to one message element. The mediation configuration is not correct.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3453W: An attempt to delete an element using a target which matches no message elements ''target'' {0}
- Explanation: The target must be a valid XPath expression that resolves to one message element.
- User Action: Verify the configuration of the mediation primitive.
- CWSXM3454E: property ''value'' {0} is not compatible with property ''type'' {1}
- Explanation: The value must be compatible with the type specified. The mediation configuration is not correct.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3455E: property ''type'' {0} is not compatible with existing ServiceMessageObject property at path ''target'' {1} of ''type'' {2}
- Explanation: The message element must be compatible with the exsisting SMO property being set.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3456E: property ''value'' {0} is an XPath expression that resolves to more than one message element
- Explanation: The value must be a valid XPath expression that resolves to one message element. The mediation configuration is not correct.
- User Action: Correct the configuration of the mediation primitive.
- CWSXM3500E: Unable to send the event to the Common Event Infrastructure. Refer to the nested exception for more information.
- Explanation: An exception occurred when sending an event to the Common Event Infrastructure service.
- User Action: Inspect the nested exception to diagnose the problem.
- CWSXM3501E: The event label property {0} has a length of {1} which exceeded the maximum length of 64 characters.
- Explanation: The event label exceeded the maximum length of 64 characters.
- User Action: Reduce the value of the event label property to 64 or less characters.
- CWSXM3502E: Unable to send the event to the Common Event Infrastructure. Ensure that the Common Event Infrastructure is available.
- Explanation: The event emitter primitive was unable to send the event to the Common Event Infrastructure.
- User Action: Ensure that the Common Event Infrastructure and associated resources are available for access.
- CWSXM3550E: Unable to connect to the service registry defined by ''{0}''. Refer to the nested exception for more information.
- Explanation: Unable to connect to the service registry. The nested exception, if available, will contain more information.
- User Action: Ensure that the service registry is available and administration settings for the service registry definition have been correctly configured.
- CWSXM3551E: Service registry definition ''{0}'' set on node ''{1}'' in module ''{2}'' could not be found.
- Explanation: The service registry definition could not be found.
- User Action: Ensure a service registry definition is configured with the required definition name or a default service registry definition exists.
- CWSXM3552E: User property ''{0}'' has in invalid xpath value ''{1}''.
- Explanation: The primitive has been configured with a user property that has in invalid xpath value.
- User Action: Ensure that the path specified is a valid location within the Service Message Object.
- CWSXM3553E: Authentication error for service registry definition ''{0}''. Either the specified authentication alias does not exist or the supplied credentials are incorrect.
- Explanation: Either the specified authentication alias for registry definition does not exist, or the supplied credentials are incorrect.
- User Action: Ensure the authentication alias exists and has the correct credentials are supplied.
- CWSXM3554E: The registry URL supplied for service registry definition ''{0}'' is malformed.
- Explanation: The registry URL supplied in the service registry definition is malformed.
- User Action: Ensure that the registry URL is correctly specified in the service registry definition.
- CWSXM3555E: The service registry connection type specified by service registry definition ''{0}'' is not supported.
- Explanation: The service registry connection type specified by the service registry definition is not supported.
- User Action: Select a supported connection type for the service registry definition.
- CWSXM3556E: The service registry proxy for service registry definition ''{0}'' is not initialized.
- Explanation: The service registry proxy is not initialized.
- User Action: Ensure that the server started correctly. This error can result from a previous failure.
- CWSXM3557E: The service registry proxy for service registry definition ''{0}'' cannot be found.
- Explanation: The service registry proxy cannot be found. The nested exception, if available, will contain more information.
- User Action: Ensure that the server started correctly. This error can result from a previous failure.
- CWSXM3558E: The action requested by the Endpoint Lookup Mediation Primitive ''{0}'' in module ''{1}'' is not supported.
- Explanation: The action requested by the Endpoint Lookup Mediation Primitive is not supported.
- User Action: Ensure that the server started correctly. This error can result from a previous failure.
- CWSXM3559E: The service registry proxy request has failed.
- Explanation: The service registry proxy request has failed.
- User Action: Ensure that the server started correctly. This error can result from a previous failure.
- CWSXM3560E: The parameters passed to the service registry proxy are incorrect.
- Explanation: The parameters passed to the service registry proxy are incorrect.
- User Action: Ensure that the server started correctly. This error can result from a previous failure.
- CWSXM3561E: A service registry exception has occured when node ''{1}'' in module ''{2}'' invoked the service registry specified by service registry definition ''{0}''. The exception message is ''{3}''.
- Explanation: A service registry exception. The nested exception, if available, will contain more information.
- User Action: Inspect the nested exception to diagnose the problem.
- CWSXM3562E: The service registry specified by service regsitry definition ''{0}'' invoked by node ''{1}'' in moudule ''{2}'' has retuned an invalid result.
- Explanation: The service registry has retuned an invalid result. The nested exception, if available, will contain more information.
- User Action: Ensure the server and service registry have started without error.
- CWSXM3563E: An unexpected exception has been thrown by node ''{1}'' in moudule ''{2}'' when trying to invoke the service reqistry specified by service registry definition ''{0}''.
- Explanation: An unexpected exception has been thrown when trying to invoke the service registry. The nested exception, if available, will contain more information.
- User Action: Inspect the nested exception to diagnose the problem.
- CWSXM3564E: A service registry proxy exception has occured when node ''{1}'' in module ''{2}'' invoked the service registry specified by service registry definition ''{0}''. The exception message is ''{3}''.
- Explanation: A service registry proxy exception. The nested exception, if available, will contain more information.
- User Action: Inspect the nested exception to diagnose the problem.
- CWSXM4000E: Error parsing the Mediation Flow definition: unexpected format.
- Explanation: Found at runtime while trying to parse the Mediation Flow file produced by the tooling.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4001E: Error parsing the Mediation Flow definition: cannot parse the terminal type.
- Explanation: Found at runtime while trying to parse the Mediation Flow file produced by the tooling.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4002E: Error parsing the Mediation Flow definition: Response flow with no preceding Request flow.
- Explanation: The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4003E: Error parsing the Mediation Flow definition: there are no flows.
- Explanation: The Mediation Flow definition should start with one Request Flow and may contain additional request and Response Flows.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4004E: Error parsing the Mediation Flow definition: no Operation Name for node, ''{0}''.
- Explanation: Missing value for the named node''s Operation Name.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4005E: Error parsing the Mediation Flow definition: no Reference Name for node, ''{0}''.
- Explanation: Missing value for the named node''s Reference Name.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4006E: Error parsing the Mediation Flow definition: no Operation Name for the Custom Mediation node, ''{0}'' (of type ''{1}'').
- Explanation: Missing value for the Custom Mediation node''s Operation Name.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4007E: Error parsing the Mediation Flow definition: no Reference Name for the Custom Mediation node, ''{0}'' (of type ''{1}'').
- Explanation: Missing value for the Custom Mediation node''s Reference Name.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4008E: Error parsing the Mediation Flow definition: node name, ''{0}''.
- Explanation: An exception occurred when parsing the named mediation flow node. Check the causal exception information for more detail.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4010E: Error parsing the Mediation Flow definition: found {0} InputNodes.
- Explanation: The Request Flow must have one, and only one Input node.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4011E: Error parsing the Mediation Flow definition: Request Flow, Operation Name=''{0}''.
- Explanation: An exception occurred when parsing the named mediation flow Request Flow. Check the causal exception information for more detail.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4012E: Error parsing the Mediation Flow definition: Response Flow.
- Explanation: An exception occurred when parsing the mediation flow Response Flow. Check the causal exception information for more detail.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4013E: Error parsing the Mediation Flow definition: Terminal types do not match.
- Explanation: The types of the terminals that are connected together must be the same.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4014E: Error parsing the Mediation Flow definition: Node, ''{0}'' has an incorrectly defined or missing terminal.
- Explanation: The node is missing an expected terminal, named with one of the standard names, ''in'' or ''out''.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4019E: Error parsing the Mediation Flow definition: Node ''{0}'' is an unidentified type of node (''{1}''): not standard, nor mediation primitive, nor custom mediation node.
- Explanation: The Mediation Flow definition file may have been corrupted or the Mediation Flow may have been produced on a version of the tooling greater than the version of the runtime.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4025E: Error parsing the Mediation Flow definition: missing value for source Terminal type.
- Explanation: No value for the sub-type of the complex-type for a source terminal in a connection.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4026E: Error parsing the Mediation Flow definition: missing value for target Terminal type.
- Explanation: No value for the sub-type of the complex-type for a target terminal in a connection.
- User Action: Verify that the Mediation Flow definition is correct.
- CWSXM4100E: Mediation flow component definition file {0} could not be loaded.
- Explanation: The named mediation flow component definition file could not be loaded.
- User Action: Check the validity of the deployed mediation component.
- CWSXM4101E: Mediation flow definition file {0} could not be loaded.
- Explanation: The named mediation flow definition file could not be loaded.
- User Action: Check the validity of the deployed mediation component.
- CWSXM4102E: Error in parsing mediation flow component definition file {0}: {1}
- Explanation: An exception occurred when parsing the named mediation flow component definition file. Check the causal exception information for more detail.
- User Action: Check the validity of the deployed mediation component.
- CWSXM5000E: Error occurred when attempting to load the mediation flow component defintion file {0}: {1}
- Explanation: An exception occurred when attmepting the load the mediation flow component defintion file. Check the causal exception information for more detail.
- User Action: Check that the location of the file exists and is accessible.
- CWSXM5001E: Error occurred when parsing the mediation flow component definition file: {0}
- Explanation: An exception occurred when attmepting the parse the mediation flow component defintion file. Check the causal exception information for more detail.
- User Action: Check the validity of the mediation flow component definition file.
- CWSXM5002E: Error occurred when attempting to resolve the message body type {0} for the mediation flow component defintion file {1}: {2}
- Explanation: An exception occurred when attempting to resolve the message body type. Check the causal exception information for more detail.
- User Action: Check the validity of the mediation flow component definition file.
- CWSXM5003E: Error occurred when attempting to resolve the property values from the server configuration.
- Explanation: An exception occurred when attempting to resolve the property valyes from the server configuration.
- User Action: Ensure that the server is running and the application containing the mediation configuration flow definition file is deployed. Alternatively configure the event generation application to use the default values specified in the mediation flow component defintion file
- CWSXM5004E: Error occurred when attempting to resolve the input message schema defined on the event emitter ''in'' terminal
- Explanation: An exception occurred when attempting to resolve the input message schema defined on the event emitter ''in'' terminal. Check the causal exception information for more detail.
- User Action: Check the validity of the mediation flow component definition file.
- CWSXM9998I: This is a test message
- Explanation: This is a unit test message
- User Action: No action necessary
- CWSXM9999I: This is a test parameterised message: {0}
- Explanation: This is a unit test message
- User Action: No action necessary