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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
Problem | Message selectors are only supported for API messages. |
User response | Ensure that the application does not use message selectors for non-API messages. |
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/. |
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/. |
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/. |
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/. |
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. |
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. |
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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
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. |
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. |
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. |
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. |
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/. |
Problem | The file included a nested resource, and errors were found while loading the nested resource. |
User response | See previous messages for further information. |
Problem | An exception was thrown while looking up the Ecore model. |
User response | See previous messages for further information. |
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. |
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. |
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. |
Problem | An error was reported while importing an XML Schema. |
User response | Refer to the error message for more information. |
Problem | The BLOB Data Access Service was unable to parse the message. |
User response | See previous messages for further information. |
Problem | The BLOB Data Access Service was unable to calculate the message length. |
User response | See previous messages for further information. |
Problem | The BLOB Data Access Service was unable to write the message. |
User response | See previous messages for further information. |
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. |
Problem | The SOAP Data Access Service was unable to parse the message. |
User response | See previous messages for further information. |
Problem | The SOAP Data Access Service was unable to calculate the message length. |
User response | See previous messages for further information. |
Problem | The SOAP Data Access Service was unable to write the message. |
User response | See previous messages for further information. |
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. |
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. |
Problem | The SOAP Data Access Service was unable to create a new DataGraph. |
User response | See previous messages for further information. |
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. |
Problem | The XML parser has reported an error while processing a SOAP message. |
User response | Ensure the message is well-formed XML. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Problem | The JMF Data Access Service was unable to parse the message. |
User response | See previous messages for further information. |
Problem | The JMF Data Access Service was unable to calculate the message length. |
User response | See previous messages for further information. |
Problem | The JMF Data Access Service was unable to write the message. |
User response | See previous messages for further information. |
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/. |
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. |
Problem | The Bean Data Access Service was unable to parse the message. |
User response | See previous messages for further information. |
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. |
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. |
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. |
Problem | The Bean Data Access Service was unable to write the message. |
User response | See previous messages for further information. |
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. |
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. |
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. |
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. |
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. |
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. |
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(). |
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. |
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. |
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. |
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. |
Problem | The Bean Data Access Service was unable to create a new DataGraph. |
User response | See previous messages for further information. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Problem | The message format provided does not match an expected message format. |
User response | Ensure a correct message format is provided. |
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. |
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 |
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 |
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. |
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 |
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. |
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. |
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. |
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 |
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. |
Problem | The access of a JMS Map Message through SDO is not supported. |
User response | Rewrite the application to use supported function. |
Problem | The serialization of the payload datagraph failed. |
User response | Examine the linked exception to determine the problem. |
Problem | The parsing of the byte array to create the datagraph failed. |
User response | Examine the linked exception to determine the problem. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Problem | An unexpected error occurred while configuring an XML parser. |
User response | Examine the linked exception to determine the problem. |
Problem | The payload of the JMS stream message is not valid XML. |
User response | Examine the linked exception to determine the problem. |
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. |
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. |
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. |
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. |
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. |
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/. |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | See previous messages for further information. |