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 the error or the exception stack trace to determine the 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 the service to use. |
Action | Modify the client deployment descriptor to add a <service-qname> element or modify the WSDL file to contain 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 with the deployment descriptor that is listed. |
Action | Correct the problem with the deployment descriptor. |
Explanation | An error was issued with the deployment descriptor that is listed. |
Action | Correct the error with the deployment descriptor. |
Explanation | A fatal error was issued with the deployment descriptor that is listed. |
Action | Correct the fatal error with the deployment descriptor. |
Explanation | WebSphere Application Server was unable to locate the Web container during Web services startup. |
Action | Correct the problems with WebSphere Application Server startup. |
Explanation | The value for the scope is not valid. |
Action | Correct the scope in the binding file to one of 'Request', 'Application', or 'Session'. |
Explanation | The global configuration file (was-webservices.xml) defines a provider, which specifies a Java class that cannot be loaded. |
Action | Determine and correct the cause of the failure. |
Explanation | Either a servlet whose name matches the servlet-link is not found for a port component, or the Web application is not a servlet. |
Action | Use a valid servlet name in the '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 file that is specified in the Web services client deployment descriptor cannot be read. |
Action | Make sure that the file name that is specified in the Web service client deployment descriptor references a valid JAX-RPC mapping file in the module. |
Explanation | An error occurred in the handler configuration. The ignored handler might 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 | An error occurred in the handler configuration. The ignored handler might 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 | An error occurred in the 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 the services to deploy. |
Explanation | An unexpected type of client reference was 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 | 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 | The resource cannot be loaded by the class or 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 resource cannot be loaded by the class or 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 enterprise bean collaborator cannot 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 cannot 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 cannot 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 cannot 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 cannot 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 global configuration file (was-webservices.xml) defines a handler that specifies a Java class that cannot be loaded. |
Action | Determine and fix the cause of the failure to load the specified Java class. |
Explanation | The port component binding is not required, but certain functionality is not available without it. |
Action | No user action is required. |
Explanation | An exception was generated and the context information is being created. |
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 file that is named in the Web services deployment descriptor cannot be found in this module. |
Action | Make sure that the file name that is specified in the Web service deployment descriptor refers to an existing file in the module. |
Explanation | The service name cannot be changed from the default name that is generated in the service locator because a setter method for the service name cannot be found. |
Action | Regenerate the client-side artifacts, including the ServiceLocator class with the WebSphere Application Server emitters. |
Explanation | The noted file is required to make this type of module available as a Web service. |
Action | Make sure that the module in the application contains the required binding file. |
Explanation | The file is not required, but certain functionality is not available without it. |
Action | No user action is required. |
Explanation | The Web service description binding is not required, but certain functionality is not available without it. |
Action | No user action is 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 the endptEnabler tool. |
Explanation | One or more of the values for the defaultMappings information in the client bindings file cannot be found in the WSDL file. |
Action | Verify and correct the defaultMappings information in the client bindings file. |
Explanation | The J2EE 1.3 Web services client deployment descriptor file, webservicesclient.xml, contains unexpected component-scoped service references for a J2EE Web application or application client module. |
Action | Remove the component-scoped service references from the webservicesclient.xml file. |
Explanation | The J2EE 1.3 Web services client deployment descriptor file, webservicesclient.xml, must contain component-scoped service referencess for a J2EE enterprise bean component. |
Action | Add component-scoped service references to the webservicesclient.xml file for enterprise bean components. |
Explanation | The deployment descriptor has component-scoped references, but their component names do not match any enterprise bean names in the module. |
Action | Remove the webservicesclient.xml file, or correct the component names. |
Explanation | The Web service-enabled enterprise bean is missing the protocol specification (HTTP, JMS, and so on). |
Action | Redeploy the Web service-enabled enterprise bean with a valid protocol. |
Explanation | The service endpoint is required for a web service-enabled enterprise bean. The service endpoint is not defined in the ejb-jar.xml file for the specified enterprise bean. |
Action | Define a service-endpoint for the enterprise bean in the ejb-jar.xml file. |
Explanation | The service endpoint in the ejb-jar.xml and webservices.xml files must match. |
Action | Correct the service endpoint for the ejb-jar.xml and webservices.xml files. |
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 <ejb-link> value must match an existing <ejb-name> value. |
Action | Change the <ejb-link> value to match the <ejb-name> value of the proper enterprise bean. |
Explanation | The service qname that is specified in the service reference does not match any services that are specified in the WSDL file. |
Action | Review and correct the service reference's service qname. |
Explanation | A request has been received for a system application that is not installed and deployed. |
Action | Verify the system endpoint name and check for errors during server startup. |
Explanation | No router is defined for the incoming request. |
Action | Verify that valid system services endpoints exist with valid system endpoint configuration files. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
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, no user action is required. |