WebSphere Process Server messages     Operating Systems: All supported

WSWS

WSWS1000E: Error: {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/.
WSWS1001E: The client process service cannot be accessed.
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/.
WSWS1002E: An error occurred while processing the Web services deployment descriptor for module: {0} with error: {1}
Problem Unable to construct a Web services deployment descriptor.
User response Review the error or the exception stack trace to determine the cause.
WSWS1003E: The WSDL file that is referenced by the client deployment descriptor service reference {0} contains no services.
Problem There are no services defined in the WSDL file.
User response Modify the WSDL file to include at least one service definition.
WSWS1004E: An error occurred while binding client references in java:{0} namespace: {1}
Problem Unable to bind client references into the JNDI namespace.
User response This exception is unexpected. The cause is not immediately known.
WSWS1005E: The DTD reference in the Web services deployment descriptor is not valid: {0}
Problem Invalid DTD reference in Web services deployment descriptor.
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/.
WSWS1007E: More than one service is in the WSDL file, but service reference {0} in the client deployment descriptor does not specify which service QName to use.
Problem If there is more than one service in the WSDL file, the client deployment descriptor must specify a QName of the service to use.
User response Modify the client deployment descriptor to add a <service-qname> element or modify the WSDL file to contain only one service.
WSWS1008W: Unable to dump the configuration as part of debug: {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/.
WSWS1009W: Warning: [{0}:{1}:{2}] {3}
Problem A warning was issued with the deployment descriptor that is listed.
User response Correct the problem with the deployment descriptor.
WSWS1010E: Error: [{0}:{1}:{2}] {3}
Problem An error was issued with the deployment descriptor that is listed.
User response Correct the error with the deployment descriptor.
WSWS1011E: Error: [{0}:{1}:{2}] {3}
Problem A fatal error was issued with the deployment descriptor that is listed.
User response Correct the fatal error with the deployment descriptor.
WSWS1012E: Error: Web services is missing the Web container.
Problem WebSphere Application Server was unable to locate the Web container during Web services startup.
User response Correct the problems with WebSphere Application Server startup.
WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
Problem The value for the scope is not valid.
User response Correct the scope in the binding file to one of 'Request', 'Application', or 'Session'.
WSWS1014W: Java class {0} that is specified in provider {1} cannot be loaded. The provider is skipped. The exception is {2}.
Problem The global configuration file (was-webservices.xml) defines a provider, which specifies a Java class that cannot be loaded.
User response Determine and correct the cause of the failure.
WSWS1015W: Servlet for servlet-link {0} not found. The port-component {1} is skipped.
Problem Either a servlet whose name matches the servlet-link is not found for a port component, or the Web application is not a servlet.
User response Use a valid servlet name in the 'servlet-link' field and verify that the Web application is a servlet.
WSWS1016E: Multiple 'port-component-name' elements with the value {0} were found.
Problem The port-component-name values must be unique.
User response Use unique port-component-names.
WSWS1017E: The JSR 109 JAX-RPC mapping file {0}, as specified in the client deployment descriptor for service reference {1} cannot be read.
Problem The JAX-RPC mapping file that is specified in the Web services client deployment descriptor cannot be read.
User response 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.
WSWS1018W: For handlers {0} the handler {1} was not added due to a role statement {2} that is not valid.
Problem An error occurred in the handler configuration. The ignored handler might cause unexpected results.
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/.
WSWS1019W: For handlers {0} the handler {1} is not added because of a flow statement {2} that is not valid.
Problem An error occurred in the handler configuration. The ignored handler might cause unexpected results.
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/.
WSWS1020E: Unable to parse file {0}
Problem An error occurred in the configuration.
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/.
WSWS1021W: Warning: No services to deploy.
Problem No (zero) services found to deploy.
User response Specify the services to deploy.
WSWS1022W: Client reference {0} not of expected type {1} in java:comp namespace.
Problem An unexpected type of client reference was found in the namespace.
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/.
WSWS1023W: The client reference was not found in java:comp namespace.
Problem The reference was not found in the namespace.
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/.
WSWS1025E: Error: Resource {0} was not found.
Problem The resource cannot be loaded by the class or system class loaders.
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/.
WSWS1026E: Error: Resource {0} was not loaded: {1}
Problem The resource cannot be loaded by the class or system class loaders.
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/.
WSWS1027W: Warning: Web services MBean could not be registered: {0}
Problem The MBean could not be registered.
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/.
WSWS1028E: Error: Unable to initialize EJBCollaborator: {0}
Problem The Web services enterprise bean collaborator cannot be initialized.
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/.
WSWS1029E: Error: {0}: Metadata service lookup failed: {1}
Problem The Metadata service cannot be found.
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/.
WSWS1030E: An error occurred while binding service references: {0}
Problem The service reference cannot be bound.
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/.
WSWS1031E: {0}: An error occurred while binding service references in the java:{1} namespace.
Problem The service reference cannot be bound into the namespace.
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/.
WSWS1032E: {0}: An error occurred while binding service reference {1} in the java:{2} namespace.
Problem The service reference cannot be bound into the namespace.
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/.
WSWS1033W: Java class {0} that is specified for handler {1} cannot be loaded. The handler is skipped. The exception is {2}.
Problem The global configuration file (was-webservices.xml) defines a handler that specifies a Java class that cannot be loaded.
User response Determine and fix the cause of the failure to load the specified Java class.
WSWS1034W: No port component binding with the name {0} was found in bindings file {1}.
Problem The port component binding is not required, but certain functionality is not available without it.
User response No user action is required.
WSWS1035E: An error occurred in {0}: context information: {1}
Problem An exception was generated and the context information is being created.
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/.
WSWS1037E: The JSR 109 JAX-RPC mapping file {0}, as specified in <webservice-description> {1} in deployment descriptor {2} for module {3} was not found in application {4}. This Web service description is ignored.
Problem The required JAX-RPC mapping file that is named in the Web services deployment descriptor cannot be found in this module.
User response Make sure that the file name that is specified in the Web service deployment descriptor refers to an existing file in the module.
WSWS1038W: No setter method on {0} with a method name {1} was found for reference {2}. The service name cannot be changed to {3}.
Problem 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.
User response Regenerate the client-side artifacts, including the ServiceLocator class with the WebSphere Application Server emitters.
WSWS1039E: The Web services binding file {0} was not found in module {1} in application {2}. This file is required for this type of module.
Problem The noted file is required to make this type of module available as a Web service.
User response Make sure that the module in the application contains the required binding file.
WSWS1040W: The Web services binding file {0} was not found in module {1} in application {2}. Certain functionality, such as Web services security is not available.
Problem The file is not required, but certain functionality is not available without it.
User response No user action is required.
WSWS1041W: No Web service description binding is found in the Web services binding file {0} with the name {1}.
Problem The Web service description binding is not required, but certain functionality is not available without it.
User response No user action is required.
WSWS1042E: An error occurred in loading the configuration for {0}. The exception is {1}.
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/.
WSWS1043E: An error occurred in the configuration. More than one security binding is defined, but the program cannot determine which one to use without the WSDL service port.
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/.
WSWS1044E: An error occurred in the configuration. More than one security deployment descriptor is defined, but the program cannot determine which one to use without the WSDL service port.
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/.
WSWS1045E: An error occurred in loading {0} configuration for {1}. The service cannot be started.
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/.
WSWS1046E: The ibm-webservices-bnd.xmi file for enterprise bean module {0} says that the associated router module is {1}. However, that router module does not exist in the application.
Problem The router module is missing from the application.
User response Fix the application by running the endptEnabler tool.
WSWS1047W: The ibm-webservicesclient-bnd.xmi defaultMappings information for serviceRefLink {0} does not correspond to the information in the WSDL file. One or more of the following values are incorrectly specified in the ibm-webservicesclient-bnd.xmi file: portTypeLocalName {1}, portTypeNamespace {2}, portLocalName {3}, or portNamespace {4}.
Problem One or more of the values for the defaultMappings information in the client bindings file cannot be found in the WSDL file.
User response Verify and correct the defaultMappings information in the client bindings file.
WSWS1048E: J2EE 1.3 {0} contains unexpected component-scoped service references with no component specified.
Problem 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.
User response Remove the component-scoped service references from the webservicesclient.xml file.
WSWS1049E: J2EE 1.3 {0} is missing component-scoped service references.
Problem The J2EE 1.3 Web services client deployment descriptor file, webservicesclient.xml, must contain component-scoped service referencess for a J2EE enterprise bean component.
User response Add component-scoped service references to the webservicesclient.xml file for enterprise bean components.
WSWS1050W: J2EE 1.3 {0} component-scoped service references do not match the enterprise beans.
Problem The deployment descriptor has component-scoped references, but their component names do not match any enterprise bean names in the module.
User response Remove the webservicesclient.xml file, or correct the component names.
WSWS1051W: The Web service-enabled enterprise bean does not have any defined Web service router modules.
Problem The Web service-enabled enterprise bean is missing the protocol specification (HTTP, JMS, and so on).
User response Redeploy the Web service-enabled enterprise bean with a valid protocol.
WSWS1052E: The service endpoint is not defined. Application ''{0}'', Module ''{1}'', enterprise bean ''{2}''.
Problem 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.
User response Define a service-endpoint for the enterprise bean in the ejb-jar.xml file.
WSWS1053E: The service endpoint of the ejb-jar.xml ({0}) and webservices.xml ({1}) files do not match. Application ''{2}'', Module ''{3}'', enterprise bean ''{4}''.
Problem The service endpoint in the ejb-jar.xml and webservices.xml files must match.
User response Correct the service endpoint for the ejb-jar.xml and webservices.xml files.
WSWS1054E: Internal Error: An EJB object is expected at dispatcher invoke.
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/.
WSWS1055E: Internal Error: An EJB object is expected at dispatcher cleanup.
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/.
WSWS1056E: Internal Error: The method ''{0}'' on class ''{1}''was not found.
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/.
WSWS1057E: Internal Error: The Web services global configuration was not loaded.
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/.
WSWS1058E: Application {0}, module {1}, file {2}, port-component-name {3}: service-impl-bean ejb-link {4} does not correspond to any enterprise bean name in the ejb-jar.xml file.
Problem The <ejb-link> value must match an existing <ejb-name> value.
User response Change the <ejb-link> value to match the <ejb-name> value of the proper enterprise bean.
WSWS1059E: No WSDL services exist with qname {0}.
Problem The service qname that is specified in the service reference does not match any services that are specified in the WSDL file.
User response Review and correct the service reference's service qname.
WSWS1060E: Received request {0} for unregistered system service endpoint {1}.
Problem A request has been received for a system application that is not installed and deployed.
User response Verify the system endpoint name and check for errors during server startup.
WSWS1061E: No system endpoint router is defined for request {0}.
Problem No router is defined for the incoming request.
User response Verify that valid system services endpoints exist with valid system endpoint configuration files.
WSWS1062I: The SOAP Container service has been initialized.
Problem This informational message indicates the program status.
User response No user action is required.
WSWS1063E: No Web services system service is available.
Problem The configuration for the Web services system service is not available.
User response Verify that the Web services system service configuration files are correct.
WSWS1064E: A transport header key of null or length of zero is specified. This header key is not valid and will be ignored.
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/.
WSWS1065E: A transport header value of null or length of zero is specified for header key {0}. This header key is not valid and will be ignored.
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/.
WSWS1066W: {0} in {1} does not contain a componentScopedRefs element, which is required for configuring security.
Problem A componentScopedRefs element is missing from one of the .xmi files. A componentScopedRefs element is not required unless you are configuring security.
User response If configuring security, add a componentScopedRefs element to the specified xmi file. Otherwise, no user action is required.
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.webservices.resources.webservicesMessages.html

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