WebSphere Process Server messages     Operating Systems: All supported

CWSIF

CWSIF0001E: A JsMessageFactoryImpl instance cannot be created: exception {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0011E: A JsJmsMessageFactoryImpl instance cannot be created: exception {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0021E: A TrmMessageFactoryImpl instance cannot be created: exception {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0031E: A JsMessageHandleFactoryImpl instance cannot be created: exception {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0041E: A ControlMessageFactoryImpl instance cannot be created: exception {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0051E: A CompHandshakeImpl instance cannot be created: exception {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0061E: A {0} instance cannot be created: exception {1}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0101E: Message selectors are not supported for message {0}.
Problem Message selectors are only supported for API messages.
User response Ensure that the application does not use message selectors for non-API messages.
CWSIF0102E: Message type {1} was expected but message type {0} was found.
Problem An attempt was made to convert the message from one message type to another message type. This conversion is not supported.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0103E: Message type {0} with format {1} can not be converted to a JMS message as adapter type {2} is not valid.
Problem An attempt was made to convert the message from one message type to another message type. This conversion is not supported.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0181E: The SDO DataGraph cannot be obtained from the message payload.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0182E: The message contains an incorrect encapsulation class: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0191E: The hexadecimal string {0} is incorrectly formatted for a correlation ID.
Problem The string is not a valid hexadecimal correlation ID. It must be of the form ID: followed by an even number of hexadecimal characters only.
User response Correct the string for which the conversion is failing.
CWSIF0200E: The hexadecimal string {0} is incorrectly formatted.
Problem An attempt to convert from a string to byte array failed due to the string either containing non-hexadecimal characters, or an odd number of characters.
User response Check the content of the string for which the conversion is failing.
CWSIF0211E: The message format cannot be identified: exception {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0212E: The message length cannot be calculated: exception {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0213E: The message cannot be calculated: exception {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0214E: The JMF message cannot be unassembled: exception {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0221E: JMF schema ID error: exception {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0222E: The message cannot be parsed: exception {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0232E: Unable to import WSDL file {0}: exception {1}
Problem The WSDL importer was unable to import the file.
User response Ensure that you are importing valid WSDL files, and that you are using a supported version of the WSDL standard.
CWSIF0233E: Unable to locate type: name {0}, namespace {1}.
Problem The WSDL importer was unable to locate a type definition.
User response Ensure that you have included an XML Schema definition of the type in the WSDL types section.
CWSIF0234E: Unable to locate element: name {0}, namespace {1}.
Problem The WSDL importer was unable to locate an element definition.
User response Ensure that you have included an XML Schema definition of the element in the WSDL types section.
CWSIF0235E: Blocking access to input stream for URI: {0}.
Problem The run-time environment blocked access to the given URI. This is caused by an attempt to load an XML Schema that has not been deployed to the SDO repository.
User response Ensure that you have deployed appropriate WSDL and XML Schema files to the SDO repository.
CWSIF0236E: Blocking access to output stream for URI: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0237E: An exception was raised while loading included resource. Resource URI: {0}, exception: {1}.
Problem The file included a nested resource, and errors were found while loading the nested resource.
User response See previous messages for further information.
CWSIF0238E: An exception was raised while locating Ecore model. Target namespace {0}, location hint {1}, exception {2}.
Problem An exception was thrown while looking up the Ecore model.
User response See previous messages for further information.
CWSIF0240E: Unable to locate WSDL {0} with name {1}. The definition was referenced within file {2}.
Problem The WSDL importer was unable to locate a definition referenced within the WSDL.
User response Ensure that your WSDL definitions are complete, and that you have included all referenced WSDL files.
CWSIF0241E: Unable to import XML Schema file {0}: exception {1}
Problem The XML Schema importer was unable to import the file.
User response Ensure that you are importing valid XML Schema files, and that you are using a supported version of the XML Schema standard.
CWSIF0242E: Error loading XML Schema: {0}
Problem The XML Schema importer was unable to load the file.
User response Ensure that you are importing valid XML Schema files, and that you are using a supported version of the XML Schema standard.
CWSIF0243E: {0}
Problem An error was reported while importing an XML Schema.
User response Refer to the error message for more information.
CWSIF0251E: Unable to parse message: exception {0}
Problem The BLOB Data Access Service was unable to parse the message.
User response See previous messages for further information.
CWSIF0252E: Unable to calculate message length: exception {0}
Problem The BLOB Data Access Service was unable to calculate the message length.
User response See previous messages for further information.
CWSIF0253E: Unable to write message: exception {0}
Problem The BLOB Data Access Service was unable to write the message.
User response See previous messages for further information.
CWSIF0254E: Incorrect message model: type name {0}, namespace {1}.
Problem The message is based on a message model that the BLOB Data Access Service is unable to handle. The message may have been processed with the wrong Data Access Service.
User response If your message should be processed with another Data Access Service ensure that the message format is set correctly.
CWSIF0271E: Unable to parse message: exception {0}
Problem The SOAP Data Access Service was unable to parse the message.
User response See previous messages for further information.
CWSIF0272E: Unable to calculate message length: exception {0}
Problem The SOAP Data Access Service was unable to calculate the message length.
User response See previous messages for further information.
CWSIF0273E: Unable to write message: exception {0}
Problem The SOAP Data Access Service was unable to write the message.
User response See previous messages for further information.
CWSIF0274E: Incorrect format string: {0}
Problem The format string does not match the syntax required by the SOAP Data Access Service.
User response Ensure the message format follows the correct syntax for the SOAP Data Access Service.
CWSIF0275E: Incorrect buffer offsets: Buffer length {0}, Start offset {1}, data length {2}.
Problem The start offset and data length are incompatible with the buffer length passed to the SOAP Data Access Service.
User response Ensure the region described by the start offset and data length fits within the buffer.
CWSIF0276E: Unable to create a new SDO DataGraph: exception {0}
Problem The SOAP Data Access Service was unable to create a new DataGraph.
User response See previous messages for further information.
CWSIF0281E: Header entry contains wrong number of child data objects. Expected 1, found {0}.
Problem The data object representing a header entry did not contain the correct number of child data objects.
User response Ensure that each header entry contains exactly one child.
CWSIF0291E: Unable to parse the message. Error URI {0}, error code {1}, additional data {2}
Problem The XML parser has reported an error while processing a SOAP message.
User response Ensure the message is well-formed XML.
CWSIF0293E: Unexpected element found. Element name {0}, element namespace {1}.
Problem The SOAP Parser expected a SOAP Envelope element, but encountered the above element.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0294E: Unexpected element found. Element name {0}, element namespace {1}.
Problem The SOAP Parser expected a SOAP Header or Body element, but encountered the above element.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0295E: Unexpected mustUnderstand value found. Element name {0}, element namespace {1}, mustUnderstand value {2}.
Problem The SOAP Parser found a SOAP mustUnderstand attribute with an incorrect value.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0296E: Incorrect non-root SOAP body element found. Element name {0}, element namespace {1}.
Problem The SOAP Parser found a non-root SOAP body element, but the element is not SOAP encoded.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0297E: Incorrect SOAP root attribute found. Element name {0}, element namespace {1}, SOAP root attribute value {2}.
Problem The SOAP Parser found an element with an incorrect SOAP root attribute.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0298E: Data found within nil element. Element name {0}, element namespace {1}, data {2}.
Problem The SOAP Parser encountered data within an element that had an xsi:nil="true" attribute.
User response Ensure the data in the message is compatible with the XML Schema specification.
CWSIF0299E: Element found within nil element. Element name {0}, element namespace {1}, nested element name {2}, nested element namespace {3}
Problem The SOAP Parser encountered an element within an element that had an xsi:nil="true" attribute.
User response Ensure the data in the message is compatible with the XML Schema specification.
CWSIF0300E: Attribute found within nil element. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3}
Problem The SOAP Parser encountered an attribute within an element that had an xsi:nil="true" attribute.
User response Ensure the data in the message is compatible with the XML Schema specification.
CWSIF0301E: Unable to parse a value within the message. Type name {0}, type namespace {1}, data {2}
Problem The SOAP parser was unable to convert the value into an instance of the type.
User response Ensure the data in the message is compatible with the types modelled in the WSDL.
CWSIF0302E: Unexpected text found. Element name {0}, element namespace {1}, data {2}
Problem The XML element contained some text, but the WSDL model does not allow this element to contain data.
User response Ensure the data in the message is compatible with the types modelled in the WSDL.
CWSIF0303E: Incorrect xsi:type attribute encountered while processing element name {0}, namespace {1}, xsi:type value {2}
Problem The XML element contained an xsi:type attribute, but the value of the attribute could not be processed.
User response Ensure the data in the message is compatible with the XML Schema specification.
CWSIF0304E: The message body did not match any of the definitions in the WSDL
Problem The message body in the SOAP message did not match any of the definitions in the WSDL. This may be because the SOAP message is incorrect or the format string may have identified the wrong WSDL.
User response Ensure the data in the message is compatible with the WSDL.
CWSIF0305E: An id attribute cannot be found for a non-root SOAP body element. Element details: name {0}, namespace {1}.
Problem Each non-root SOAP body element should have an id attribute with a unique value.
User response Ensure that your message follows the SOAP encoding rules.
CWSIF0306E: An element with id attribute value {0} is not referenced.
Problem Each non-root SOAP body element should be referenced by some other part of the message.
User response Ensure that your message follows the SOAP encoding rules.
CWSIF0307E: An element which matches href attribute value {0} cannot be found.
Problem A SOAP encoded element uses a href attribute but an element with a matching id attribute cannot be found.
User response Ensure that your message follows the SOAP encoding rules.
CWSIF0308E: Unexpected processing instruction found. Element name {0}, element namespace {1}, target {2}.
Problem The XML element contained a processing instruction, but SOAP does not allow elements to contain processing instructions.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0309E: Unexpected element found. Element name {0}, element namespace {1}.
Problem The XML element contained simple value, but the value does not fit into the data graph.
User response Ensure the data in the message is compatible with the types modelled in the WSDL.
CWSIF0310E: Unexpected attribute found. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3}.
Problem The XML element contained an attribute, but the attribute does not fit into the data graph.
User response Ensure the data in the message is compatible with the types modelled in the WSDL.
CWSIF0311E: Unable to parse message: exception {0}
Problem The JMF Data Access Service was unable to parse the message.
User response See previous messages for further information.
CWSIF0312E: Unable to calculate message length: exception {0}
Problem The JMF Data Access Service was unable to calculate the message length.
User response See previous messages for further information.
CWSIF0313E: Unable to write message: exception {0}
Problem The JMF Data Access Service was unable to write the message.
User response See previous messages for further information.
CWSIF0314E: Message length {0} does not match the expected length {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF0315E: Incorrect format string: {0}
Problem The format string does not match the syntax required by the JMF Data Access Service.
User response Ensure the message format follows the correct syntax for the JMF Data Access Service.
CWSIF0321E: Unable to parse message: exception {0}.
Problem The Bean Data Access Service was unable to parse the message.
User response See previous messages for further information.
CWSIF0322E: Failed to create DataObject: parent type name {2}, property name {0}, namespace {1}.
Problem The Bean Data Access Service was unable to create a DataGraph representing the message.
User response Ensure that you have imported WSDL or XML Schema definitions for the message.
CWSIF0323E: Unable to determine base type for restriction derived type: type name {0}, namespace {1}.
Problem The Bean Data Access Service was unable to create a DataGraph representing the message.
User response Ensure that the WSDL or XML Schema definitions for the message are correct.
CWSIF0324E: Failed to acquire and invoke a method while introspecting an Object representing an enumerated type: type name {0}, namespace {1}, method name {2}, target class name {3}.
Problem The Bean Data Access Service was unable to create a message from the DataGraph.
User response Ensure that the supplied Java Objects feature appropriate accessor methods.
CWSIF0325E: Unable to write message: exception {0}.
Problem The Bean Data Access Service was unable to write the message.
User response See previous messages for further information.
CWSIF0326E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
Problem The Bean Data Access Service was unable to create a message from the DataGraph.
User response Ensure that the supplied Java Objects feature appropriate accessor methods.
CWSIF0327E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
Problem The Bean Data Access Service was unable to create a message from the DataGraph.
User response Ensure that the supplied Java Objects feature appropriate accessor methods.
CWSIF0328E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
Problem The Bean Data Access Service was unable to create a message from the DataGraph.
User response Ensure that the supplied Java Objects feature appropriate accessor methods.
CWSIF0329E: Failed to parse MIME attachment: content type {0}.
Problem The Bean Data Access Service was unable to create a DataObject representing the MIME attachment.
User response Ensure that the supplied Java Objects are appropriate.
CWSIF0330E: Failed to create DataObject for SOAP fault message: fault feature name {0}, namespace {1}, location {2}.
Problem The Bean Data Access Service was unable to create a DataGraph representing the message.
User response Ensure that WSDL or XML Schema definitions are available for the message.
CWSIF0331E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
Problem The Bean Data Access Service was unable to create a DataGraph representing the message.
User response Ensure that the supplied Java Objects feature appropriate accessor methods.
CWSIF0332E: Failed to create a new instance of a bean Object: parent type name {2}, property name {0}, namespace {1}, class name {3}.
Problem The Bean Data Access Service was unable to create a message from the DataGraph.
User response Ensure that the bean Object can be instantiated via Class.newInstance().
CWSIF0333E: Failed to locate model for creation of DataObject representing SOAP-encoded array message: namespace {0}, location {1}.
Problem The Bean Data Access Service was unable to create a DataGraph representing the message.
User response Ensure that WSDL or XML Schema definitions are available for the message.
CWSIF0334E: Failed to locate model for creation of DataObject representing SOAP-encoded array message: namespace {0}, location {1}.
Problem The Bean Data Access Service was unable to create a DataGraph representing the message.
User response Ensure that WSDL or XML Schema definitions are available for the message.
CWSIF0335E: Failed to write MIME attachment: content type {0}, content transfer encoding {1}, content id {2}.
Problem The Bean Data Access Service was unable to create a MIME attachment from the DataGraph.
User response Ensure that the data in the message is suitable for MIME body part creation.
CWSIF0336E: Failed to write fault message: message name {0}, operation name {1}.
Problem The Bean Data Access Service was unable to create a Detail Element from the DataGraph.
User response Ensure that the data in the message is suitable for Detail Element creation.
CWSIF0338E: Unable to create a new SDO DataGraph: exception {0}
Problem The Bean Data Access Service was unable to create a new DataGraph.
User response See previous messages for further information.
CWSIF0341E: Unable to parse message: exception {0}.
Problem The Bean Data Access Service delegated this operation to the JMF Data Access Service which was unable to parse the message.
User response See previous messages for further information.
CWSIF0342E: Unable to write message: exception {0}.
Problem The Bean Data Access Service delegated this operation to the JMF Data Access Service which was unable to write the message.
User response See previous messages for further information.
CWSIF0343E: Unable to calculate message length: exception {0}.
Problem The Bean Data Access Service delegated this operation to the JMF Data Access Service which was unable to calculate the message length.
User response See previous messages for further information.
CWSIF0346E: Failed to process attribute value: type name {0}, namespace {1}, attribute value {2}.
Problem The Bean Data Access Service was unable to map the supplied attribute value to the supplied type.
User response Ensure that the supplied attribute value is of an appropriate type.
CWSIF0347E: Failed to map schema type to a Java Class: type name {0}, namespace {1}.
Problem The Bean Data Access Service was unable to map the supplied type to a Java Class.
User response Ensure that an appropriate mapping has been provided.
CWSIF0348E: Failed to map schema type to a Java Class: type name {0}, namespace {1}.
Problem The Bean Data Access Service was unable to map the supplied type to a Java Class.
User response Ensure that an appropriate mapping has been provided.
CWSIF0350E: Incorrect format string: {0}.
Problem The format string does not match the syntax required by the Bean Data Access Service.
User response Ensure the message format follows the correct syntax for the Bean Data Access Service.
CWSIF0353E: Failed to locate metadata for message. Service namespace {0}, service name {1}, port name {2}, operation name {3}, message name {4}.
Problem The SOAP Parser was unable to locate the message metadata for the given message.
User response Ensure that you have imported WSDL definitions for the message.
CWSIF0354E: Unexpected element found within message part. Message part name {0}, Element name {1}, element namespace {2}.
Problem The SOAP Parser was processing a message part whose content is delegated to a MIME attachment, but the part also contained a nested element.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0355E: Unexpected attribute found within message part. Message part name {0}, Attribute name {1}, attribute namespace {2}.
Problem The SOAP Parser was processing a message part whose content is delegated to a MIME attachment, but the part also contained an unexpected attribute.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0356E: Unable to process MIME attachment. Message part name {0}, exception {1}.
Problem The SOAP Parser encountered an exception while processing a MIME attachment referenced by the message part.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0357E: Unable to locate MIME attachment. Message part name {0}, reference {1}.
Problem The SOAP Parser could not find the MIME attachment referenced by the message part.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0358E: Unable to process MIME attachment. Content ID {0}, Content type {1}, exception {2}.
Problem The SOAP Parser encountered an IOException while processing a MIME attachment with the given content id and type.
User response Ensure the data in the message is compatible with the SOAP specification.
CWSIF0362E: The message format {0} is incorrect
Problem The message format provided does not match an expected message format.
User response Ensure a correct message format is provided.
CWSIF0371E: The supplied value {0} is not valid for the parameter {1} of method {2}
Problem A parameter value was supplied that is not permitted for the defined method.
User response Ensure valid parameters are passed to the method in question.
CWSIF0372E: An IOException occurred while obtain the content of the message element.
Problem It was not possible to deserialize the message element due to the linked IOException
User response Investigate and resolve the problem described in the linked IOException
CWSIF0373E: An Exception occurred during the copying of a message element: {0}.
Problem It was not possible to copy a message element due to the linked Exception.
User response Investigate and resolve the problem described in the linked Exception
CWSIF0381E: The supplied value {0} is not valid for the parameter {1} of method {2}
Problem A parameter value was supplied that is not permitted for the defined method.
User response Ensure valid parameters are passed to the method in question.
CWSIF0382E: An IOException occurred while serializing or deserializing the message in method {0}
Problem It was not possible to serialize or deserialize the message element due to the linked IOException
User response Investigate and resolve the problem described in the linked IOException
CWSIF0383E: The MimeElementList only supports MimeElement entries. The supplied parameter was of type {0}.
Problem The MimeElementList is a specialised list implementation that supports only MimeElement list entries.
User response Create a MimeElement object containing the parameter before trying to add it to the list.
CWSIF0384E: The supplied message is of type {0}, and is not the required type of multipart/related.
Problem The implementation does not supported the type of the supplied message.
User response Do not supply messages of the specified type to this utility.
CWSIF0385E: {0} ContentType header entries were found in the message.
Problem The implementation only supports messages that contain exactly one ContentType header field.
User response Do not supply messages containing zero, or more than one content-type fields to this utility.
CWSIF0386E: An Exception occurred during the copying of a message element list: {0}.
Problem It was not possible to copy a message element list due to the linked Exception.
User response Investigate and resolve the problem described in the linked Exception
CWSIF0431E: The WSDL Part {0} in message {1} is not associated with a type or element.
Problem Each part of a WSDL message must be associated with a XML Schema type or element.
User response Ensure that the definition of each message part includes either the 'type' or 'element' attribute.
CWSIF0500E: A JMS Map Message can not be accessed as an SDO DataGraph.
Problem The access of a JMS Map Message through SDO is not supported.
User response Rewrite the application to use supported function.
CWSIF0501E: An error occurred while attempting to access a message''s payload datagraph as a byte array. The linked exception is {0}.
Problem The serialization of the payload datagraph failed.
User response Examine the linked exception to determine the problem.
CWSIF0502E: An error occurred while attempting to create a message''s payload datagraph from a byte array using format {0}. The linked exception is {1}.
Problem The parsing of the byte array to create the datagraph failed.
User response Examine the linked exception to determine the problem.
CWSIF0503E: The Transcoding from format {0} to format {1} is not supported.
Problem The Transcoding between the current SDO message datagraph format and the new datagraph format is not supported.
User response Rewrite the application to use supported function.
CWSIF0504E: An error occurred while attempting to create a message''s payload datagraph from a null byte array argument using format {0}. The linked exception is {1}.
Problem A non-null byte array is required to build a datagraph of this format.
User response Examine the linked exception to determine the problem.
CWSIF0600E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The WSDL could not be located.
Problem The WSDL identified by the format string could not be located. This may be because the location in the format is incorrect or because the WSDL has not been deployed.
User response Ensure that the WSDL location in the format string is correct.
CWSIF0601E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The WSDL was located, but did not contain the named service.
Problem The format string did not match the definitions in the WSDL. This may be because the service name or namespace in the format is incorrect or the wrong WSDL has been deployed.
User response Ensure that the service name and namespace in the format string match definitions in the WSDL.
CWSIF0602E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The service was located, but did not contain the named port.
Problem The format string did not match the definitions in the WSDL. This may be because the port name in the format is incorrect or the wrong WSDL has been deployed.
User response Ensure that the port name in the format string matches the definition in the WSDL.
CWSIF0603E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The port was located, but did not contain a reference to a binding.
Problem The format string did not match the definitions in the WSDL. This may be because the WSDL is incomplete or the wrong WSDL has been deployed.
User response Ensure that the port is associated with a binding in the WSDL.
CWSIF0700E: The map message does not have an equal number of names and values
Problem The map name list and map value lists must be the same length. Together they represent the name and value pairs of the map message.
User response Ensure both lists have the same length.
CWSIF0711E: Incorrect format string: {0}
Problem The format string does not match any of the format strings recognised by the JMS Data Access Service.
User response Ensure the message format follows is correct for a message type supported the JMS Data Access Service.
CWSIF0712E: The JMS message cannot be serialized, exception: {0}
Problem The program is attempting to serialize a JMS message and has failed to do so.
User response Examine the linked exception to determine the problem.
CWSIF0713E: A DataObject of type {0} is not suitable as the payload of a JMS message.
Problem The program is attempting to verify the suitability of a supplied DataObject for forming the payload of a JMS message.
User response Modify the program to supply a DataObject of an appropriate type.
CWSIF0714E: An error occurred while configuring an XML parser to read a JMS stream message; exception: {0}
Problem An unexpected error occurred while configuring an XML parser.
User response Examine the linked exception to determine the problem.
CWSIF0715E: An error occurred while parsing the payload of a JMS stream message; exception: {0}
Problem The payload of the JMS stream message is not valid XML.
User response Examine the linked exception to determine the problem.
CWSIF0716E: An input/output error occurred in the JMS Data Access Service; exception: {0}
Problem An input/output error occurred in SAX processing while trying to parse the body of a JMS stream message
User response Examine the linked exception to determine the problem.
CWSIF0717E: An input/output error occurred in the JMS Data Access Service; exception: {0}
Problem An input/output error occurred while attempting to write a JMS stream message payload.
User response Examine the linked exception to determine the problem.
CWSIF0718E: An error has occurred while trying to write a JMS stream message containing an element of type {0}.
Problem The type of the element in question is not permitted in a JMS stream message.
User response Modify the program to ensure that objects of this type are not inserted into the stream message.
CWSIF0719E: An error occurred while writing the payload of a JMS stream message; exception: {0}
Problem An unexpected error has occurred while writing the payload of a JMS stream message to bytes.
User response Examine the linked exception to determine the problem.
CWSIF0720E: An error occurred in attempting to verify the suitability of a supplied DataObject of type {0} to form the payload of a JMS message with format {1}.
Problem The type of the DataObject supplied as the payload of a JMS message must be compatible with the format of that message.
User response Modify the program to ensure that the supplied DataObject and format are compatible.
CWSIF0721E: An error occurred in class initialization, exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIF9999E: {0}
Problem If the message does not give sufficient information, check previous messages for further help.
User response See previous messages for further information.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.sib.mfp.CWSIFMessages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)