Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The request message contained multiple reference parameters with the same name, preventing the application server from targeting the correct resource. |
Action | Ensure that each reference parameter has a unique name. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The WS-Addressing feature that is enabled and the endpoint reference specied must comply with the same WS-Addressing specification. |
Action | Ensure that if you use the appropriate endpoint reference class for the WS-Addressing feature that has been enabled. |
Explanation | The name of the wsdl:service element does not match the specified name. |
Action | Ensure that the service name in the endpoint reference metadata matches the service name in the WSDL. |
Explanation | The name of the wsdl:port element does not match the specified name. |
Action | Ensure that the port name in the endpoint reference metadata matches a port name in the WSDL. |
Explanation | An attempt was made to create an endpoint reference using a null value for the address URI. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to create an endpoint reference for an endpoint identified by the service name and port name, but an address URI could not be located for that endpoint. |
Action | Ensure that the endpoint is a part of the same application as the one that is attempting to create the endpoint reference. |
Explanation | An attempt was made to create an endpoint reference, but insufficient information was provided to do so. |
Action | If the address is null then the service name and port name must be specified. On the client, the address must be specified. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the accompanying error messages for more information. |
Explanation | An attempt was made to use a class that is not supported. |
Action | Use one of the supported classes for endpoint references. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Result object cannot be null. |
Action | Provide a Result object that is not null. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the accompanying error messages for more information. |
Explanation | The service name must be set before the port name can be set. |
Action | Ensure that the service name is set before attempting to set the port name. |
Explanation | The reference parameter object cannot be null. |
Action | Provide a reference parameter object that is not null. |
Explanation | 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. |
Action | Do not set the specified property for two-way message exchange patterns. |
Explanation | The Web Services Addressing SPI was used to set the specified property, using an object that was not of the required type. |
Action | 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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the accompanying error messages for more information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the accompanying error messages for more information. |
Explanation | 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. |
Action | Ensure that if the SOAPAction and the wsa:Action are set that both values match. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the accompanying error messages for more information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | If you set both properties, they must specify the same WS-Addressing namespace. |
Action | 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. |
Explanation | The OMElement object to be converted cannot be null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The qname object cannot be null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The application attempted to convert a null endpoint reference using the EndpointReferenceConverter class. |
Action | Provide an endpoint reference that is not null. |
Explanation | 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. |
Action | 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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | 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. |
Action | 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. |
Explanation | A virtual host is a configuration entity that enables a single host machine to resemble multiple host machines. Each virtual host has a logical name and a list of one or more domain name system (DNS) aliases by which it is known. IP addresses and localhost are not automatically resolved to host names, so they should be entered as separate aliases. |
Action | Ensure all the virtual host aliases containing an IP address or localhost also have separate aliases for the corresponding host name. |
Explanation | An HTTP router module is a Web Archive (WAR) module that provides an HTTP endpoint for each of the Web services contained within a particular enterprise bean JAR module. |
Action | When your enterprise archive (EAR) file contains enterprise JavaBeans (EJB) modules that contain Web services, you must run the endptEnabler command-line tool or an assembly tool before deployment to produce a Web services endpoint Web archive (WAR) file. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See the accompanying error messages for more information. |