WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


WSWS

WSWS1000E: Error: {0}
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/.
WSWS1001E: Error - Could not access the client process 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/.
WSWS1002E: Error processing Web services deployment descriptor for module: {0} with error: {1}
Explanation Unable to construct a Web services deployment descriptor.
Action Review error (exception stack trace) for root cause.
WSWS1003E: There are no services in the WSDL file referenced by Client DD service reference {0}.
Explanation There are no services defined in the WSDL file.
Action Modify the WSDL file to include at least one service definition.
WSWS1004E: Error 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: Invalid DTD reference in Web services deployment descriptor: {0}
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/.
WSWS1007E: There is more than one service in the WSDL file but service reference {0} in the Client DD 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 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.
WSWS1008W: Unable to dump configuration as part of debug: {0}
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/.
WSWS1009W: Warning: [{0}:{1}:{2}] {3}
Explanation A warning was issued w/the deployment descriptor listed.
Action Correct the problem with the deployment descriptor.
WSWS1010E: Error: [{0}:{1}:{2}] {3}
Explanation An error was issued w/the deployment descriptor listed.
Action Correct the error with the deployment descriptor.
WSWS1011E: Error: [{0}:{1}:{2}] {3}
Explanation A fatal error was issued w/the deployment descriptor listed.
Action Correct the fatal error with the deployment descriptor.
WSWS1012E: Error: Web services missing WebContainer.
Explanation WebSphere unable to locate WebContainer during Web services startup.
Action Correct problems with WebSphere startup.
WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
Explanation Invalid value for scope.
Action Correct scope in binding file to one of 'Request', 'Application', or 'Session'.
WSWS1014W: Javaclass {0} specified in provider {1} could not be loaded. The provider will be skipped. The exception is {2}.
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.
WSWS1015W: Servlet for servlet-link {0} not found. The port-component {1} will be skipped.
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.
WSWS1016E: Found multiple port-component-name elements with the value {0}.
Explanation The port-component-name values must be unique.
Action Use unique port-component-names.
WSWS1017E: The JSR 109 JAX-RPC mapping DD file {0} as specified in the Client DD for service reference {1} could not be read.
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.
WSWS1018W: For handlers {0} the handler {1} was not added due to an invalid role statement {2}
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/.
WSWS1019W: For handlers {0} the handler {1} was not added due to an invalid flow statement {2}
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/.
WSWS1020E: Unable to parse file {0}
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/.
WSWS1021W: Warning: No services to deploy.
Explanation No (zero) services found to deploy.
Action Specify services to be deployed.
WSWS1022W: Client reference {0} not of expected type {1} in java:comp namespace.
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/.
WSWS1023W: Client reference not found in java:comp namespace.
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/.
WSWS1025E: Error: Resource {0} not found.
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/.
WSWS1026E: Error: Resource {0} not loaded: {1}
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/.
WSWS1027W: Warning: Web services MBean could not be registered: {0}
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/.
WSWS1028E: Error: Unable to initialize EJBCollaborator: {0}
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/.
WSWS1029E: Error: {0}: Meta Data service lookup failed: {1}
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/.
WSWS1030E: Error binding service references: {0}
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/.
WSWS1031E: Error: {0}: Error binding service references in java:{1} namespace.
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/.
WSWS1032E: Error: {0}: Error binding service reference {1} in java:{2} namespace.
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/.
WSWS1033W: Javaclass {0} specified for handler {1} could not be loaded. The handler will be skipped. The exception is {2}.
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.
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 will not be available without it.
Action No action required.
WSWS1035E: Exception caught in {0}: context info: {1}
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/.
WSWS1037E: The JSR 109 JAX-RPC mapping DD file {0} as specified in <webservice-description> {1} in DD {2} for module {3} was not found in application {4}. This WebServiceDescription will be ignored.
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.
WSWS1038W: No setter on {0} with a method name {1} found for reference {2}. The service name could not be changed to {3}.
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.
WSWS1039E: The IBM Web services binding file {0} was not found in module {1} in application {2}. This file is required for this type of module.
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.
WSWS1040W: The IBM Web services binding file {0} was not found in module {1} in application {2}. Certain functionality such as WS-Security will not be available.
Explanation The file is not required, but certain functionality will not be available without it.
Action No action required.
WSWS1041W: No Web service description binding was found in the IBM Web services binding file {0} with the name {1} .
Explanation The Web service description binding is not required, but certain functionality will not be available without it.
Action No action required.
WSWS1042E: Error in loading configuration for {0}. The exception is {1}.
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/.
WSWS1043E: Error in the configuration. There are more than one security bindings defined, but can not determined which one to use without the WSDL service Port.
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/.
WSWS1044E: Error in the configuration. There are more than one security deployment descriptors defined, but can not determined which one to use without the WSDL service Port.
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/.
WSWS1045E: Error in loading {0} configuration for {1}. The service can not be started.
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/.
WSWS1046E: The ibm-webservices-bnd.xml for EJB module {0} says that the associated router module is {1}. However that the router module does not exist in the application.
Explanation The router module is missing from the application.
Action Fix the application by running endpointEnabler 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 are incorrectly specified in the ibm-webservicesclient-bnd.xmi file: portTypeLocalName {1}, portTypeNamespace {2}, portLocalName {3}, and/or portNamespace {4}.
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.
WSWS1048E: J2EE 1.3 {0} contains unexpected component scoped service-refs, no component specified.
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.
WSWS1049E: J2EE 1.3 {0} missing component scoped service-refs.
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.
WSWS1050W: J2EE 1.3 {0} component scoped service-refs do not match EJBs
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.
WSWS1051W: Web Service enabled EJB does not have any defined web service router modules.
Explanation Web Service enabled EJB missing protocol (HTTP, JMS, etc).
Action Re-deploy Web service enabled EJB with a protocol specified.
WSWS1052E: Service-endpoint not defined. Application "{0}", Module "{1}", EJB "{2}".
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.
WSWS1053E: Service-endpoint of ejb-jar.xml ({0}) and webservices.xml ({1}) do not match. Application ''{2}'', Module ''{3}'', EJB ''{4}''.
Explanation Service-endpoint in ejb-jar.xml and webservices.xml must match.
Action Correct service-endpoint for ejb-jar.xml and webservices.xml.
WSWS1054E: Internal Error: expected EJB object at dispatcher invoke.
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/.
WSWS1055E: Internal Error: expected EJS object at dispatcher cleanup.
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/.
WSWS1056E: Internal Error: Could not find method ''{0}'' on class ''{1}''.
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/.
WSWS1057E: Internal Error: Web Services global configuration not loaded.
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/.
WSWS1058E: Application {0}, module {1}, file {2}, port-component-name {3}: service-impl-bean ejb-link {4} does not correspond to any ejb-name in ejb-jar.xml.
Explanation ejb-link must match an existing ejb-name
Action Change ejb-link to the ejb-name of the proper EJB.
WSWS1059E: No WSDL Services with qname {0}.
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.
WSWS1060E: Recieved request {0} for unregistered system service endpoint {1}.
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.
WSWS1061E: No system endpoint router defined for request {0}.
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.
WSWS1062I: SOAP Container Service has been initialized.
Explanation The SOAP Container Service has not been initialized.
Action None. This is an information-only message.
WSWS1063E: No Web services system service 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: An invalid transport header key of null or length of zero was specified. This header key will be ignored.
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/.
WSWS1065E: An invalid transport header value of null or length of zero was specified for header key {0}. This header key will be ignored.
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/.
WSWS1066W: WARNING: {0} in {1} does not contain a 'componentScopedRefs' element, which is required if 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, you can ignore this warning.
Reference topic    

Terms of Use | Feedback

Last updated: Apr 23, 2009 7:19:30 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.resources.webservicesMessages.html

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