Express (Distributed operating systems), v8.0 > Reference > Messages
WSWS
WSWS1000E: Error: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1001E: The client process service cannot be accessed.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1002E: An error occurred while processing the Web services deployment descriptor for module: {0} with error: {1}
Explanation Unable to construct a Web services deployment descriptor. Action 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.
Explanation There are no services defined in the WSDL file. Action Modify the WSDL file to include at least one service definition.
WSWS1004E: An error occurred while binding client references in java:{0} namespace: {1}
Explanation Unable to bind client references into the JNDI namespace. Action This exception is unexpected. The cause is not immediately known.
WSWS1005E: The DTD reference in the Web services deployment descriptor is not valid: {0}
Explanation The Web services deployment descriptor contained a DTD reference that was not valid. Action More info at:
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.
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.
WSWS1008W: Unable to dump the configuration as part of debug: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1009W: Warning: [{0}:{1}:{2}] {3}
Explanation A warning was issued with the deployment descriptor that is listed. Action Correct the problem with the deployment descriptor.
WSWS1010E: Error: [{0}:{1}:{2}] {3}
Explanation An error was issued with the deployment descriptor that is listed. Action Correct the error with the deployment descriptor.
WSWS1011E: Error: [{0}:{1}:{2}] {3}
Explanation An error was issued with the deployment descriptor that is listed. Action Correct the error with the deployment descriptor.
WSWS1012E: Error: Web services is missing the Web container.
Explanation WAS was unable to locate the Web container during Web services startup. Action Correct the problems with WAS startup.
WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
Explanation The value for the scope is not valid. Action Correct the scope in the binding file to one of 'Request', 'Application', or 'Session'.
WSWS1014W: Java class {0} specified in provider {1} cannot be loaded. The provider is skipped. The exception is {2}.
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.
WSWS1015W: Servlet for servlet-link {0} not found. The port-component {1} is skipped.
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.
WSWS1016E: Multiple ''port-component-name'' elements with the value {0} were found.
Explanation The port-component-names must be unique. Action 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.
Explanation The JAX-RPC mapping file specified in the Web services client deployment descriptor cannot 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.
WSWS1018W: For handlers {0} the handler {1} was not added due to a role statement {2} that is not valid.
Explanation An error occurred in the handler configuration. The ignored handler might cause unexpected results. Action More info at:
WSWS1019W: For handlers {0} the handler {1} is not added because of a flow statement {2} that is not valid.
Explanation An error occurred in the handler configuration. The ignored handler might cause unexpected results. Action More info at:
WSWS1020E: Unable to parse file {0}
Explanation An error occurred in the configuration. Action More info at:
WSWS1021W: Warning: No services to deploy.
Explanation No (zero) services found to deploy. Action Specify the services to deploy.
WSWS1022W: Client reference {0} not of expected type {1} in java:comp namespace.
Explanation An unexpected type of client reference was found in the namespace. Action More info at:
WSWS1023W: The client reference was not found in java:comp namespace.
Explanation The reference was not found in the namespace. Action More info at:
WSWS1025E: Error: Resource {0} was not found.
Explanation The resource cannot be loaded by the class or system class loaders. Action More info at:
WSWS1026E: Error: Resource {0} was not loaded: {1}
Explanation The resource cannot be loaded by the class or system class loaders. Action More info at:
WSWS1027W: Warning: Web services MBean could not be registered: {0}
Explanation The MBean could not be registered. Action More info at:
WSWS1028E: Error: Unable to initialize EJBCollaborator: {0}
Explanation The Web services enterprise bean collaborator cannot be initialized. Action More info at:
WSWS1029E: Error: {0}: Metadata service lookup failed: {1}
Explanation The Metadata service cannot be found. Action More info at:
WSWS1030E: An error occurred while binding service references: {0}
Explanation The service reference cannot be bound. Action More info at:
WSWS1031E: {0}: An error occurred while binding service references in the java:{1} namespace.
Explanation The service reference cannot be bound into the namespace. Action More info at:
WSWS1032E: {0}: An error occurred while binding service reference {1} in the java:{2} namespace.
Explanation The service reference cannot be bound into the namespace. Action More info at:
WSWS1033W: Java class {0} specified for handler {1} cannot be loaded. The handler is skipped. The exception is {2}.
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.
WSWS1034W: No port component binding with the name {0} was found in bindings file {1}.
Explanation The port component binding is not required, but certain functionality is not available without it. Action No user action is required.
WSWS1035E: An error occurred in {0}: context information: {1}
Explanation An exception was generated and the context information is being created. Action More info at:
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.
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 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}.
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 WAS 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.
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.
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.
Explanation The file is not required, but certain functionality is not available without it. Action No user action is required.
WSWS1041W: No Web service description binding is found in the Web services binding file {0} with the name {1}.
Explanation The Web service description binding is not required, but certain functionality is not available without it. Action No user action is required.
WSWS1042E: An error occurred in loading the configuration for {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1045E: An error occurred in loading {0} configuration for {1}. The service cannot be started.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation The router module is missing from the application. Action 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}.
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.
WSWS1048E: J2EE 1.3 {0} contains unexpected component-scoped service references with no component specified.
Explanation The Java Platform, Enterprise Edition 1.3 Web services client deployment descriptor file, webservicesclient.xml, contains unexpected component-scoped service references for a Java EE Web application or application client module. Action Remove the component-scoped service references from the webservicesclient.xml file.
WSWS1049E: J2EE 1.3 {0} is missing component-scoped service references.
Explanation The Java Platform, Enterprise Edition 1.3 Web services client deployment descriptor file, webservicesclient.xml, must contain component-scoped service referencess for a Java EE enterprise bean component. Action 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.
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.
WSWS1051W: The Web service-enabled enterprise bean does not have any defined Web service router modules.
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.
WSWS1052E: The service endpoint is not defined. Application ''{0}'', Module ''{1}'', enterprise bean ''{2}''.
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.
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}''.
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.
WSWS1054E: Internal Error: An EJB object is expected at dispatcher invoke.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1055E: Internal Error: An EJB object is expected at dispatcher cleanup.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1056E: Internal Error: The method ''{0}'' on class ''{1}''was not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1057E: Internal Error: The Web services global configuration was not loaded.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
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.
WSWS1059E: No WSDL services exist with qname {0}.
Explanation The service qname specified in the service reference does not match any services specified in the WSDL file. Action Review and correct the service reference's service qname.
WSWS1060E: Received request {0} for unregistered system service endpoint {1}.
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.
WSWS1061E: No system endpoint router is defined for request {0}.
Explanation No router is defined for the incoming request. Action Verify that valid system services endpoints exist with valid system endpoint configuration files.
WSWS1062I: The SOAP Container service has been initialized.
Explanation This informational message indicates the program status. Action No user action is required.
WSWS1063E: No Web services system service is available.
Explanation The configuration for the Web services system service is not available. Action 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.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1066W: {0} in {1} does not contain a componentScopedRefs element, which is required for configuring security.
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.
WSWS1067E: The loading of the metadata for JAX-RPC module {0} has failed. The exception is: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS1068E: Internal error. A response from a web service endpoint in an Enterprise Java Beans module could not be processed because an endpoint manager could not be located.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.