WebSphere Process Server messages     Operating Systems: All supported

CWWAR

CWWAR0001E: A SOAPElement object cannot be created from the OMElement object: {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/.
CWWAR0002E: The WS-Addressing namespace was not valid, or is not supported.
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/.
CWWAR0003E: The message context does not contain a SOAPEnvelope object.
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/.
CWWAR0004E: Multiple reference parameters exist with the same name.
Problem The request message contained multiple reference parameters with the same name, preventing the application server from targeting the correct resource.
User response Ensure that each reference parameter has a unique name.
CWWAR0100E: The {0} property cannot be set for a two-way message exchange pattern.
Problem The application attempted to set the specified property for a two-way message exchange pattern. Setting this property would prevent the client from receiving messages.
User response Do not set the specified property for two-way message exchange patterns.
CWWAR0101E: The value of the {0} message addressing property is not of the correct type. The expected type is {1}, but the actual type is {2}.
Problem The Web Services Addressing SPI was used to set the specified property, using an object that was not of the required type.
User response Provide an object of the required type for the specified property. Refer to the information center for a list of types for message addressing properties.
CWWAR0102E: A problem occurred during the conversion of an endpoint reference.
Problem This exception is unexpected. The cause is not immediately known.
User response See the accompanying error messages for more information.
CWWAR0103E: The {0} property is not a valid message addressing property.
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/.
CWWAR0104E: A problem occurred during the conversion of an attributed URI object.
Problem This exception is unexpected. The cause is not immediately known.
User response See the accompanying error messages for more information.
CWWAR0105E: The SOAPAction value {0} and the wsa:Action value {1} do not match.
Problem You can set the SOAPAction and the wsa:Action values either in the WSDL file for the Web service, or as properties using the Web Services Addressing SPI. If you set both values, using either method, the values must match.
User response Ensure that if the SOAPAction and the wsa:Action are set that both values match.
CWWAR0106E: A problem occurred during the conversion of a relationship set.
Problem This exception is unexpected. The cause is not immediately known.
User response See the accompanying error messages for more information.
CWWAR0107E: The value of the {0} internal property is not of the correct type. The expected type is {1}, but the actual type is {2}.
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/.
CWWAR0108E: The {0} WS-Addressing namespace, specified by the {1} property, conflicts with the {2} namespace of the destination endpoint reference, specified by the {3} property.
Problem If you set both properties, they must specify the same WS-Addressing namespace.
User response If you set both properties, ensure that the value of the WSADDRESSING_OUTBOUND_NAMESPACE property matches the namespace set in the endpoint reference used for the WSADDRESSING_DESTINATION_EPR property.
CWWAR0109E: The OMElement object that was provided was null.
Problem The OMElement object to be converted cannot be null.
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/.
CWWAR0110E: The qname object that was provided was null.
Problem The qname object cannot be null.
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/.
CWWAR0111E: The endpoint reference that was provided was null.
Problem The application attempted to convert a null endpoint reference using the EndpointReferenceConverter class.
User response Provide an endpoint reference that is not null.
CWWAR0112E: The {0} namespace does not match the expected namespace, {1}.
Problem The application attempted to convert an endpoint reference using the EndpointReferenceConverter class, but the namespace of the endpoint reference does not match the expected namespace.
User response When you convert an endpoint reference using the EndpointReferenceConverter class, ensure that the namespace of the endpoint reference to be converted matches the namespace that is expected for the resulting object. Refer to the information center for details of the expected namespaces.
CWWAR0200E: The address is not a valid URI object.
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/.
CWWAR0201E: The application server could not generate a unique endpoint for this service-endpoint pair. Service: {0}, Endpoint: {1}
Problem The application used the createEndpointReference(serviceName, endpointName) method of the Web Services Addressing (WS-Addressing) API to create an endpoint reference, but there are multiple Web service applications that have the same service name and endpoint name. The WS-Addressing API could not generate a unique URI object for the endpoint.
User response Ensure that all applications in the server have unique service-endpoint pairs, for example, by changing the endpoint name of an application, or by moving the application to a different server.
CWWAR9999E: {0}
Problem If the message does not give sufficient information, check previous messages for further help.
User response See the accompanying error messages for more 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.wsaddressing.jaxws.CWWARMessages.html

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