Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | Unable to construct a Web services deployment descriptor. |
Action | Review error (exception stack trace) for root cause. |
Explanation | There are no services defined in the WSDL file. |
Action | Modify the WSDL file to include at least one service definition. |
Explanation | Unable to bind client references into the JNDI namespace. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | Invalid DTD reference in Web services deployment descriptor. |
Action | 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/. |
Explanation | If there is more than one service in the WSDL file the Client Deployment Descriptor must specify a QName of which service to use. |
Action | Modify the Client Deployment Descriptor to add a <service-qname> element or modify the WSDL file to have only one service. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | A warning was issued w/the deployment descriptor listed. |
Action | Correct the problem with the deployment descriptor. |
Explanation | An error was issued w/the deployment descriptor listed. |
Action | Correct the error with the deployment descriptor. |
Explanation | A fatal error was issued w/the deployment descriptor listed. |
Action | Correct the fatal error with the deployment descriptor. |
Explanation | WebSphere unable to locate WebContainer during Web services startup. |
Action | Correct problems with WebSphere startup. |
Explanation | Invalid value for scope. |
Action | Correct scope in binding file to one of 'Request', 'Application', or 'Session'. |
Explanation | A configuration file (was-webservices.xml) defines a provider which specifies a javaclass that cannot be loaded. |
Action | Determine cause of failure to load the specified Java class, and fix. |
Explanation | Either a servlet with name matching servlet-link was not found for a port component, or the Web application is not a Servlet. |
Action | Use valid servlet name in servlet-link field and verify that the Web application is a servlet. |
Explanation | The port-component-name values must be unique. |
Action | Use unique port-component-names. |
Explanation | The JAX-RPC mapping Deployment Descriptor specified in the Web services Client Deployment Descriptor can not be read. |
Action | Make sure that the file name specified in the Web service Client Deployment Descriptor references a valid JAX-RPC Mapping file in the module. |
Explanation | Error in handler configuration. Handler ignored may cause unexpected results. |
Action | 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/. |
Explanation | Error in handler configuration. Handler ignored, may cause unexpected results. |
Action | 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/. |
Explanation | Error in configuration. |
Action | 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/. |
Explanation | No (zero) services found to deploy. |
Action | Specify services to be deployed. |
Explanation | Unexpected type of client reference in namespace. |
Action | 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/. |
Explanation | The reference was not found in the namespace. |
Action | 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/. |
Explanation | Resource not visible to class and system class loaders. |
Action | 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/. |
Explanation | Resource cannot be loaded by class and system class loaders. |
Action | 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/. |
Explanation | The MBean could not be registered. |
Action | 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/. |
Explanation | The Web services EJB Collaborator could not be initialized. |
Action | 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/. |
Explanation | The MetaData service could not be found. |
Action | 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/. |
Explanation | The service reference could not be bound. |
Action | 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/. |
Explanation | The service reference could not be bound into the namespace. |
Action | 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/. |
Explanation | The service reference could not be bound into the namespace. |
Action | 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/. |
Explanation | A configuration file (was-webservices.xml) defines a handle which specifies a javaclass that cannot be loaded. |
Action | Determine cause of failure to load the specified Java class, and fix. |
Explanation | The port component binding is not required, but certain functionality will not be available without it. |
Action | No action required. |
Explanation | Exception caught, dumping context info. |
Action | 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/. |
Explanation | The required JAX-RPC mapping Deployment Descriptor named in the Web services Deployment Descriptor can not be found in this module. |
Action | Make sure that the file name specified in the Web service Deployment Descriptor references an existing file in the module. |
Explanation | The service name could not be changed from the default name generated in the ServiceLocator because a setter for the ServiceName could not be found. |
Action | Regenerate the client side artifacts including the ServiceLocator class with the WebSphere emitters. |
Explanation | This file required in order to make this type of module available as a Web service. |
Action | Ensure the module in the application contains the indicated bindings file. |
Explanation | The file is not required, but certain functionality will not be available without it. |
Action | No action required. |
Explanation | The Web service description binding is not required, but certain functionality will not be available without it. |
Action | No action required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | The router module is missing from the application. |
Action | Fix the application by running endpointEnabler tool. |
Explanation | One or more of the values for the defaultMappings information in the client bindings file can not be found in the WSDL file. |
Action | Verify and correct the defaultMappings information in the client bindings file. |
Explanation | J2EE 1.3 Web services client deployment descriptor file, webservicesclient.xml, contains unexpected component scoped service-refs for a J2EE Web Application or Application Client module. |
Action | Remove component scoped service-refs from webservicesclient.xml. |
Explanation | J2EE 1.3 Web services client deployment descriptor file, webservicesclient.xml, must contain component scoped service-refs for a J2EE EJB component. |
Action | Add component scoped service-refs to webservicesclient.xml for EJB components. |
Explanation | DD has component scoped-refs, but their component-name(s) do not match any EJB names in module. |
Action | Removed webservicesclient.xml file, or correct component names. |
Explanation | Web Service enabled EJB missing protocol (HTTP, JMS, etc). |
Action | Re-deploy Web service enabled EJB with a protocol specified. |
Explanation | Service-endpoint is required for a web-service enabled EJB. Service-endpoint not defined in ejb-jar.xml for specified EJB. |
Action | Define service-endpoint for EJB in ejb-jar.xml. |
Explanation | Service-endpoint in ejb-jar.xml and webservices.xml must match. |
Action | Correct service-endpoint for ejb-jar.xml and webservices.xml. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | ejb-link must match an existing ejb-name |
Action | Change ejb-link to the ejb-name of the proper EJB. |
Explanation | Service qname specified in service-ref does not match any services specified in WSDL file. |
Action | Review and correct service-ref's service qname. |
Explanation | Request received for a system application that has not been installed and deployed. |
Action | Verify the system endpoint name and check for errors during server startup. |
Explanation | There is no router defined for the incoming request. |
Action | Verify that there are valid system services endpoints with valid system endpoint configuration files. |
Explanation | The SOAP Container Service has not been initialized. |
Action | None. This is an information-only message. |
Explanation | The configuration for the Web services system service is not available. |
Action | Verify that the Web services system service configuration files are correct. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | A componentScopedRefs element is missing from one of the .xmi files. A componentScopedRefs element is not required, unless you are configuring security. |
Action | If configuring security, add a componentScopedRefs element to the specified xmi file. Otherwise, you can ignore this warning. |