WebSphere Web Services messages

WSWS0001E: The path "{0}" is not an absolute path.
Explanation: The name of the published WSDL file must be an fully qualified, absolute, path name.
User Response: Provide an absolute path.

WSWS0002E: The parent directory for directory "{0}" does not exist.
Explanation: The directory into which the published WSDL file is to be placed must already exist.
User Response: Name an existing directory.

WSWS0003E: Protocol must be either "http" or "https", not "{0}".
Explanation: The only valid choices for the protocol are "http" and "https".
User Response: sSpecify either "http" or "https".

WSWS0004E: Port must be a positive number, not "{0}".
Explanation: Port must be a positive number.
User Response: Provide a positive number.

WSWS0005E: An exception occurred while attempting to extract module "{0}" from the application EAR file into the file system. The exception is "{1}".
Explanation: The exception details should provide additional information.
User Response: The exception details should give guidance on what to do.

WSWS0006E: An exception occured while attempting to construct a WSDLParser on WSDL file "{0}" in module "{1}". The exceptions is "{2}".
Explanation: The exception details should provide additional information.
User Response: The exception details should give guidance on what to do.

WSWS0007E: The Web services Deployment Descriptor "webservices.xml" for module {0} has a webservice-description element whose wsdl-file element is "{1}". The webservice-description element contains a port-component element with the elements port-qname-namespace = {2} and port-qname-localname = {3}. The wsdl file must contain a targetNameSpace whose value matches the binding file's port-qname-namespace, and it must contain a port whose name attribute matches the port-qname-localname.
Explanation: The values in the wsdl file and the Web services Deployment Descriptor must match up.
User Response: Correct one of the files.

WSWS0008E: Cannot set the soap address into the published WSDL file. Failed when calling WSLDParser.setSoapAddress() with wsdlNameSpace={0}, wsdlPortName={1}, and soapAddressURI={2}. The input WSDL file is {3} for module {4}.
Explanation: There may be a syntax error in the input WSDL file.
User Response: Check the input WSDL file for any errors.

WSWS0009E: Caught an exception while saving input WSDL file {0} for module {1} to filename {2}. The exceptions is {3}.
Explanation: Could not create output WSDL file.
User Response: The exception details should give some guidance.

WSWS0010E: Caught an exception while creating a working directory. The exception is {0}.
Explanation: Could not create a working directory.
User Response: The exception details should give some guidance.

WSWS0011E: Caught an exception while trying to get an InputStream for file {0} in module {1}. The exception is {2}.
Explanation: Could not get the InputStream.
User Response: The exception details should give some guidance.

WSWS0012E: Failed while looking in the application ear file''s application.xml for a Web module whose name is {0}. Perhaps the EndpointEnabler has not been run on the application.
Explanation: The ibm-webservice-bnd.dtd file of Web service enabled jar file has routeModuleName attribute whose value does not match any Web module described in the application's application.xml file. Or, a Web service enabled war file does not appear i the application's application.xml file.
User Response: Check the ibm-webservice-bnd.dtd and application.xml files. Make sure the endpointEnabler has been run on the ear file.

WSWS0013E: The module {0}''s Web services Deployment Descriptor, webservices.xml, has a wsdl-file element for the file {1}. However, the module's bindingfile, {2}, doesn't have a ws-desc-binding element for that WSDL file.
Explanation: There is a mismatch between the information in the Web services Deployment Descriptor and the information in the Web services Binding file.
User Response: Make the two files consistent.

WSWS0015E: Caught an exception while trying to get an InputStream for file {0}. The exception is {1}.
Explanation: The exception details should provide additional information.
User Response: The exception details should give some guidance.

WSWS0016E: The webservices.xml file for module {0} refers to WSDL file "{1}", but the module does not contain a WSDL file by that name.
Explanation: If a webservices.xml file has a reference to a WSDL file then that WSDL file must exist in the module.
User Response: Add the expected WSDL file.

WSWS0018E: The module {0} does not contain a Web services binding file, {1}. Run the endptEnabler command on the EAR file before installing to add this file.
Explanation: A Web service enabled module must contain a Web services binding file.
User Response: Add the missing binding file using either the Assembly Toolkit or the endptEnabler command.

WSWS0019E: The resource bundle {0} for locale {1} could not be opened. Exception {2}
Explanation: The resource bundle for your locale was not found. This will prevent logging of information.
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/.

WSWS0020E: Internal Error: {0}
Explanation: 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/.

WSWS0021E: In the Web services Deployment Descriptor for module "{0}", there is no wsdl-file element for webservice-deployment descriptor number {1}.
Explanation: The Web services Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a wsdl-file element.
User Response: Fix the DeploymentDescriptor.

WSWS0022E: In the Web services Deployment Descriptor for module "{0}", the portcomponent element number {1} of webservice-description element number {2} is not properly formed.
Explanation: The Web services Deployment Descriptor is not properly formed, one if its webservice-description elements has an improperly formed portcomponent element.
User Response: Fix the DeploymentDescriptor.

WSWS0023E: The Web services bindings file, {0}, for module {1} does not contain any properly formatted routerModules elements
Explanation: The Web services binding file does not contain a properly formatted "routerModules" element.
User Response: Fix the bindings file.

WSWS0024E: A Web services enabled EJB-JAR module must be deployed to the same server as its router module. However the EJB-JAR module "{0}" is deployed to "{1}" while its router module. "{2}" is deployed to "{3}".
Explanation: Each EBJ-JAR file must have a related router WAR module.
User Response: Fix the application.

WSWS0025E: Caught an Exception while copying a file. The source file is {0}. The target file is {1}. The exception is {2}.
Explanation: An IOException occurred while copying a file.
User Response: The exception details should give some guidance.

WSWS0026E: The file system name "{0}" is needed for a directory in the published WSDL file tree. However, the name already exists in the file system and is not a directory.
Explanation: There is a name conflict between directory and file system name.
User Response: Remove the file.

WSWS0027E: In the Web services Deployment Descriptor for module "{0}", there is no webservice-description-name element for webservice-deployment descriptor number {1}.
Explanation: The Web services Deployment Descriptor is not properly formed, one if its webservice-description elements does not have a webservice-description-name element.
User Response: Fix the DeploymentDescriptor.

WSWS0028W: completeTask : Cannot close InputStream "{0}"
Explanation: 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/.

WSWS0029E: getServerName: MapModulesToServers :taskData did not contain a row for moduleURIString "{0}"
Explanation: This is a programming error. All the modules shouldhave server names.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS0030E: MapModulesToServersAccessor.getNodeNamesFromServerString: the string "{0}" does not have the correct syntax.
Explanation: This is a programming error. Assume that theMapModulesToServers task should have already validated thatthe user input has the correct syntax.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS0031E: If a servlet is linked to a webservice.xml file'''s port-component, then the module'''s web.xml file must contain no more than one servlet-mapping for that servlet. However, in module {0}, web.xml contains more than one servlet-mapping element for servlet {1}.
Explanation: The web.xml file contains an error.
User Response: Repair the web.xml file.

WSWS0032E: If a servlet is linked to from a webservice.xml file'''s port-component, and the module'''s web.xml file contains a url-pattern for that servlet, then the url-pattern must be an exact match pattern, that is it must not contain an asterisk("*"). However, in module {0}, web.xml contains a url-pattern of {1} for servlet {2}.
Explanation: The web.xml file contains an error.
User Response: Repair the web.xml file.

WSWS0033E: In the webservices.xml file for a Web services enabled WAR module, a port-component''s service-impl-bean must be servlet-link, not an EJB-link. However in module {0}, webservice.xml has a port-component named {1} whose service-impl-bean is not a servlet-link.
Explanation: The webservices.xml file contains an error.
User Response: Repair the webservices.xml file.

WSWS0034E: In module {0}, the WSDL file {1} contains a port named {2}, but there is no corresponding port component in the Web services deployment descriptor.
Explanation: One of the WSDL files in a module is inconsistent with the Web services deployment descriptor.
User Response: remove the inconsistency, either by removing the port from the WSDL file or adding a corresponding port-component to the Deployment Descriptor.

WSWS0035E: The ibm-webservices-bnd.xml for EJB module {0} says that the associated router WAR module is {1}. However that WAR module does not exist in the application.
Explanation: The router war module is missing from the application.
User Response: Fix the application.

WSWS0036E: {0} is the router module for Web services enabled module {1}. The router modules web.xml file must contain a servlet-mapping stanza with a url-pattern and a servlet-name of {2}, but it does not.
Explanation: The router WAR's web.xml is not correct.
User Response: Make sure the servlet-mapping element is there and that it contains a url-pattern.

WSWS0037W: The module {0} contains WSDL file {1}. It is recommended that WSDL files reside in or below WEB-INF/wsdl (for WAR modules) and META-INF/wsdl (for JAR modules).
Explanation: Older versions of Web services specification allowed the wsdl-file element of the Web services Deployment Descriptor to point anywhere in the module. The current version recommends that all WSDL files reside in or below WEB-INF/wsdl (for WAR modules) and META-INF/wsdl (for JAR modules).. In the future, WSDL files that do not reside in or below the appropriate wsdl directory will not be published to URI, or to file.
User Response: Move all WSDL files to the wsdl directory.

WSWS0038E: Error from Web services deploy tool: {0}
Explanation: Web services deploy tool reported an error, the deployment may have failed.
User Response: Examine the error message from WSDeploy tool to determine the source of the problem.

WSWS0039W: Warning from Web services deploy tool: {0}
Explanation: Web services deploy tool reports a warning, the deployment may or may not fail.
User Response: Examine the warning message from WSDeploy to determine whether any corrective action is necessary.

WSWS0040I: Message from Web services deploy tool: {0}
Explanation: None.
User Response: None.

WSWS0041I: Web services deploy task completed successfully.
Explanation: The Web services deploy task has completed successfully.
User Response: None.

WSWS0042E: The Web services bindings file for module {0} contains router module stanza whose transport type is neither jms nor http, but, incorrectly, {1}
Explanation: The Web services bindings file has incorrect information
User Response: Correct the Web services bindings file

WSWS0043E: The EJB module {0} does not have an associated router module
Explanation: For all Web services enabled EJB module, at least one router module has to be created within the same application
User Response: Run endpointEnabler to add appropriate router modules

WSWS0044E: Can not locate the deploy target for module: {0}
Explanation: All applications have to deployed into either a server or a cluster.
User Response: Correct the deployment.xml for this the application or reinstall the application.

WSWS0045E: The router war module for EJB module {0} is {1}, but its web.xml is missing a url pattern for port component {2}.
Explanation: The web.xml for the router war module should have one url pattern for each port component defined within webservices.xml.
User Response: Correct the web.xml for this router module.

WSWS0046E: The JMS router MDB module {0} does not contain a WebSphere IBM binding file.
Explanation: 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/.

WSWS0047E: Can not find any WSDL files to publish.
Explanation: All Web services enabled applications should have at least one wsdl file.
User Response: If the application is Web services enabled, check to see whether wsdl files are packaged with the application.

WSWS0048I: Web services endpointenabler task completed successfully.
Explanation: The Web services endpointenabler task has completed successfully.
User Response: None.

WSWS0049E: The EJB URL suffix {0} is not correctly formatted. It must have the form =[&=], where the valid property_names are {1}. For example {2}
Explanation: Incorrect user input for EJB URL suffix
User Response: Provide correct input.

WSWS0050E: The Web services client bind file, ibm-webservicesclient-bnd.xmi, contains port type {0} which is not a valid port type for this client.
Explanation: There is an inconsistency in the Web services client configurartion.
User Response: Ensure that the WSDL file configured for this client contains the port type.

WSWS0051W: Custom Property parameter configured for {0} module {1} was ignored.
Explanation: Only element zero of the custom property parameters object is used.
User Response: Product code should make sure the properties configured are combined into the first parameter element. Report an error to support.

WSWS0052E: Preferred port mapping could not be created for module {0} client Web service {1}
Explanation: An problem occurred while creating a mapping of port types and the ports that could be configured for them. This information is generated from the client deployment descriptor and the WSDL file.
User Response: Ensure that Web services client in this module is probably configured and the WSDL file identified in the client deployment descriptor is in the module.

WSWS0053E: The port {0} is not valid for port type {1} for Web service {2}, module {3}{4}
Explanation: A Web service client preferred port must implement its port type. The client WSDL file specifies ports, bindings and port types.
User Response: Specify a preferred port that implements the port type.

WSWS0054E: the JMS URL prefix {0} is not correctly formatted. It must start with jms:/[queue|topic]?, and the destination and connectionFactory must not contain java:comp.
Explanation: Incorrect user input for JMS URL prefix.
User Response: Provide correct input.

WSWS0055E: The value for Web service scope, {0}, for a port in module {1} is invalid.
Explanation: Incorrect user input provided for Web service scope.
User Response: Provide correct input. Correct values are Application, Request, and Session.

WSWS0056E: The value for Web service client request timeout, {0}, for a port in module {1} is invalid.
Explanation: Incorrect user input provided for Web service client resquest timeout. The timeout is number of milliseconds to wait for a request to complete.
User Response: Provide correct input. The value must be a positive integer, 0, or -1.

WSWS0057E: The value for Web service client overridden endpoint URL, {0}, for a port in module {1} is invalid.
Explanation: The user input provided for Web service client overridden endpoint URL is not a valid URL.
User Response: Provide correct input. The value must be a valid URL that represents an HTTP port, JMS port, or a local ejb.

WSWS0058E: The deployed WSDL, {0}, could not be found for the Web service client in module {1}.
Explanation: The user input provided for Web service client's deployed WSDL is invalid.
User Response: Provide correct input. The deployed WSDL value must be a uri relative to the module and represent a WSDL file that is in the client's module.

WSWS0059E: The Web service client overridden binding namespace, {0}, for module {1} cannot be specified if the overridden endpoint URL is not defined.
Explanation: The overridden binding namespace cannot be specified unless the overridden endpoint URL is specified or previously defined.
User Response: Provide a value for Web service client overridden endpoint URL or do not specify a value for the overridden binding namespace.

WSWS1000E: Error: {0}
Explanation: 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: Error - Could not access the client process service.
Explanation: 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: Error processing Web services deployment descriptor for module: {0} with error: {1}
Explanation: Unable to construct a Web services deployment descriptor.
User Response: 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.
User Response: 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.
User Response: 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.
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: 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.
User Response: Modify the Client Deployment Descriptor to add a 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.
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}
Explanation: A warning was issued w/the deployment descriptor listed.
User Response: Correct the problem with the deployment descriptor.

WSWS1010E: Error: [{0}:{1}:{2}] {3}
Explanation: An error was issued w/the deployment descriptor listed.
User Response: Correct the error with the deployment descriptor.

WSWS1011E: Error: [{0}:{1}:{2}] {3}
Explanation: A fatal error was issued w/the deployment descriptor listed.
User Response: Correct the fatal error with the deployment descriptor.

WSWS1012E: Error: Web services missing WebContainer.
Explanation: WebSphere unable to locate WebContainer during Web services startup.
User Response: Correct problems with WebSphere startup.

WSWS1013E: Error: Found illegal scope: binding file={0}, portComponentName={1}, scope={2}.
Explanation: Invalid value for scope.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
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} was not added due to an invalid flow statement {2}
Explanation: Error in handler configuration. Handler ignored, may 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}
Explanation: Error in 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.
Explanation: No (zero) services found to deploy.
User Response: 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.
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: Client reference not found in java:comp namespace.
Explanation: 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} not found.
Explanation: Resource not visible to class and 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} not loaded: {1}
Explanation: Resource cannot be loaded by class and 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}
Explanation: 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}
Explanation: The Web services EJB Collaborator could not 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}: Meta Data service lookup failed: {1}
Explanation: The MetaData service could not 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: Error binding service references: {0}
Explanation: The service reference could not 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: Error: {0}: Error binding service references in java:{1} namespace.
Explanation: The service reference could not 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: Error: {0}: Error binding service reference {1} in java:{2} namespace.
Explanation: The service reference could not 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: 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.
User Response: 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.
User Response: No action required.

WSWS1035E: Exception caught in {0}: context info: {1}
Explanation: Exception caught, dumping context info.
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 DD file {0} as specified in {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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
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: 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.
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: 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.
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: Error in loading {0} configuration for {1}. The service can not be started.
Explanation: 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.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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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).
User Response: 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.
User Response: 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.
User Response: 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.
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: expected EJS object at dispatcher cleanup.
Explanation: 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: Could not find method ''{0}'' on class ''{1}''.
Explanation: 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: Web Services global configuration not loaded.
Explanation: 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 ejb-name in ejb-jar.xml.
Explanation: ejb-link must match an existing ejb-name
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
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: 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.
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: 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.
User Response: If configuring security, add a componentScopedRefs element to the specified xmi file. Otherwise, you can ignore this warning.

WSWS2000I: {0}
Explanation: None.
User Response: No user action is required.

WSWS2001I: Trace data will be displayed on stdout.
Explanation: The requested trace data will be logged to the standard output stream.
User Response: No user action is required.

WSWS2002I: Please enter the name of an existing file.
Explanation: These are instructions for the endpoint enabler.
User Response: No user action is required.

WSWS2003I: Backing up EAR file to: {0}~
Explanation: The endpoint enabler is making a backup copy of the EAR file.
User Response: No user action is required.

WSWS2004I: IBM WebSphere Application Server Release 6
Explanation: Standard IBM banner displayed by the endpoint enabler.
User Response: No user action is required.

WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
Explanation: Standard IBM banner displayed by the endpoint enabler.
User Response: No user action is required.

WSWS2006I: Please enter the name of your EAR file:
Explanation: These are instructions for the endpoint enabler.
User Response: No user action is required.

WSWS2007I: (C) COPYRIGHT International Business Machines Corp. 1997, 2004.
Explanation: Standard IBM Copyright.
User Response: No user action is required.

WSWS2008E: Missing value for '-transport' parameter.
Explanation: The '-transport' parameter was specified on the command line but the associated value was not specified.
User Response: Specify a value for the '-transport' parameter and re-try the command.

WSWS2009E: Missing value for '-properties' parameter.
Explanation: The '-properties' parameter was specified on the command line but the associated properties filename was not specified.
User Response: Specify a properties filename for the '-properties' parameter and re-try the command.

WSWS2010I: Read properties from file: {0}
Explanation: The endpoint enabler is reading properties from the specified file.
User Response: No user action is required.

WSWS2011E: ERROR: unrecognized command-line parameter found: {0}
Explanation: The specified command-line parameter was encountered but is not a recognized as a valid command-line parameter.
User Response: Correct the command and re-try.

WSWS2012I: The endpoint enabler is using the following properties:
Explanation: Properties being used by the endpoint enabler.
User Response: No user action is required.

WSWS2013E: Unrecognized transport: {0}
Explanation: An unrecognized transport type was specified for the '-transport' command-line parameter or within a .transports property. Valid transport types are: "http" and "jms".
User Response: Ensure that only valid transport types are used on the command line and within the properties file.

WSWS2014E: 'EAR filename' parameter is missing or empty.
Explanation: A null value or empty string was passed for the 'EAR filename' parameter to the EndpointEnabler.enableEarFile method.
User Response: Ensure that a valid EAR filename is passed.

WSWS2015E: 'props' parameter is missing.
Explanation: A null value was passed for the 'props' parameter to the EndpointEnabler.enableEarFile method.
User Response: Ensure that a valid Properties object is passed for the 'props' parameter.

WSWS2016I: Loading EAR file: {0}
Explanation: The endpoint enabler has started loading the specified EAR file into memory.
User Response: No user action is required.

WSWS2017I: Found EJB Module: {0}
Explanation: The endpoint enabler recognized the specified EJB jar within the EAR file, and is processing the EJB jar.
User Response: No user action is required.

WSWS2018I: Finished processing EAR file {0}.
Explanation: The endpoint enabler has finished processing the specified EAR file.
User Response: No user action is required.

WSWS2019I: Enabling EJB Module {0}...
Explanation: The endpoint enabler has started to process the specified EJB jar module.
User Response: No user action is required.

WSWS2020I: Finished enabling EJB Module {0}...
Explanation: The endpoint enabler has finished processing the specified EJB jar module.
User Response: No user action is required.

WSWS2021I: Skipping EJB Module {0} since it contains no Web services.
Explanation: The specified EJB Module does not contain a JSR109 deployment descriptor. Therefore, it must not contain any Web services and does not need to be enabled.
User Response: No user action is required.

WSWS2022I: Skipping {0} router module for EJB Module {1} since it already contains a router for this transport.
Explanation: The specified EJB Module already contains a router module for the specified transport.
User Response: No user action is required.

WSWS2023I: Skipping {0} router for EJB Module {1} due to 'skip' property.
Explanation: The indicated router module will not be added to the EAR since the user specified a 'skip' property for the indicated EJB Module.
User Response: No user action is required.

WSWS2024I: Adding {0} router for EJB Module {1}.
Explanation: The endpoint enabler is adding a router module for the specified transport.
User Response: No user action is required.

WSWS2025I: Router module name: {0}
Explanation: The endpoint enabler is displaying the name of the new router module.
User Response: No user action is required.

WSWS2026I: Context root: {0}
Explanation: The endpoint enabler is displaying the context root for the new router module.
User Response: No user action is required.

WSWS2027I: Listener input port: {0}
Explanation: The endpoint enabler is displaying the listener port for the new router module.
User Response: No user action is required.

WSWS2028I: Destination type: {0}
Explanation: The endpoint enabler is displaying the destination type for the new router module.
User Response: No user action is required.

WSWS2029I: Enter {0} router name for EJB Module {1} [{2}]:
Explanation: The endpoint enabler is requesting a name for the router module.
User Response: Follow instructions as requested.

WSWS2030I: Enter {0} context root for EJB Module {1} [{2}]:
Explanation: The endpoint enabler is requesting the context root for a router module.
User Response: Follow instructions as requested.

WSWS2031I: Enter {0} listener input port name for EJB Module {1} [{2}]:
Explanation: The endpoint enabler is requesting the listener port name for a router module.
User Response: Follow instructions as requested.

WSWS2032E: Invalid destination type specified: {0}
Explanation: Valid destination types include 'queue' and 'topic'.
User Response: Correct the destination type and re-try.

WSWS2033I: Enter {0} destination type for EJB Module {1} [{2}]:
Explanation: Requesting the destination type for the router module.
User Response: Follow instructions as requested.

WSWS2034I: Usage syntax: endptEnabler [options] [trace options] [] represents the name of the EAR file to be processed. If not specified, the user will be prompted for this value. Options: -help, -h, -? Print this message and exit. -verbose, -v Print detailed progress messages while the EAR file is being processed. -quiet, -q Do not print progress messages while the EAR file is being processed. -properties -p Load and use the properties contained in . -transport -t The comma-separated default list of transports for which router modules should be created. The currently-supported transports include http and jms. -enableHttpRouterSecurity Each HTTP router module created by endptEnabler will be protected if the EJBs in the corresponding EJB jar are also protected. Note that if this option is not specified, then no security information will be added to the HTTP router module, even if the corresponding EJB jar contains security information. {0} Examples: endptEnabler endptEnabler myearfile.ear endptEnabler -v myearfile.ear endptEnabler -v -transports jms myearfile.ear endptEnabler -q -p myenabler.props -t http myearfile.ear
Explanation: This message explains how to invoke the endptEnabler command.
User Response: No user action is required.

WSWS2035E: Error loading the JSR 109 deployment descriptor {0} for EJB Module {1}.
Explanation: The endpoint enabler was unable to read the specified deployment descriptor file. This is possibly due to some unexpected or invalid structure within.
User Response: Please check for and correct any errors the specified file may contain.

WSWS2036I: Saving EAR file {0}...
Explanation: The endpoint enabler tool is saving the EAR file to disk.
User Response: No user action is required.

WSWS2037I: Finished saving the EAR file.
Explanation: The endpoint enabler has finished saving the EAR file to disk.
User Response: No user action is required.

WSWS2038I: Trace has been enabled for the following components: {0}
Explanation: This message tells the user that tracing has been enabled for one or more components.
User Response: No user action is required.

WSWS2039I: Trace data will be logged in file: {0}
Explanation: The requested trace data will be logged into the specified file.
User Response: No user action is required.

WSWS2040W: EJB jar {0} contains protected EJBs, yet the -enableHttpRouterSecurity option was not specified, so the resulting HTTP router module, {1}, will not include security information.
Explanation: This is simply a warning which indicates security information will not be added to the HTTP router module since the -enableHttpRouterSecurity option was not specified on the command line. If you would like the HTTP router module to be protected, simply specify the -enableHttpRouterSecurity option.
User Response: No user action is required.

WSWS2041W: The -enableHttpRouterSecurity option was specified, yet the EJB jar {0} contains at least one unprotected EJB or the existing security information is incomplete. Therefore, security information will not be added to the {1} HTTP router module.
Explanation: This is simply a warning which indicates that security information will not be added to the HTTP router module since the EJB jar does not contain complete security information. If you would like the HTTP router module to be protected, make sure that the EJB jar contains complete security information.
User Response: No user action is required.

WSWS2042E: Listener input port {0} is already configured for JMS router module {1}.
Explanation: A listener input port that is configured with a queue cannot be used with more than one JMS router module. The Web service implementations contained within a particular enterprise bean jar module share a listener input port and the associated queue, but the listener input port cannot be shared with another enterprise bean jar module.
User Response: Create a new listener input port and associate it with one of the JMS router modules.

WSWS2043I: Activation spec JNDI name: {0}
Explanation: The endpoint enabler is displaying the activation spec JNDI name for the new router module.
User Response: No user action is required.

WSWS2044I: Enter {0} Activation spec JNDI name for EJB module {1} [{2}]:
Explanation: The endpoint enabler is requesting the Activation spec JNDI name for a router module.
User Response: Follow instructions as requested.

WSWS2045I: EndpointEnabler failed with error: {0}
Explanation: The endpoint enabler encountered an error and did not succeed.
User Response: Correct the error and invoke the endpoint enabler command again.

WSWS3000I: WSDL2Java emitter Usage: WSDL2Java [options] WSDL-URI Important Options: -r, -role the J2EE role that identifies which files to generate. Valid arguments are: "develop-client" : (default) generates files for client development "develop-server" : generates files for server development "deploy-client" : generates binding files for client deployment "deploy-server" : generates binding files for server deployment "client" : combination of "develop-client" and "deploy-client" "server" : combination of "develop-server" and "deploy-server" -c, -container indicates the J2EE container. Valid arguments are: "none" : indicates no container "client" : indicates client container "ejb" : indicates EJB container "web" : indicates Web container If client role the default argument is "none". If server role the container must be either "ejb" or "web". The same container option must be used for both development and deployment. -o, -output output directory for emitted files. -m, -inputMappingFile the location of the Java to WSDL mapping. -i, -introspect introspect existing classes to determine mapping details. -C, -classpath classpath to use for class introspection. Other Options: -h, -help print this message and exit. -X, -helpX print extended options. -v, -verbose print verbose informational messages. -N, -NStoPkg = mapping of namespace to package. Alternatively declare this information in the mapping file. -O, -timeout number of seconds to wait for accessing WSDL-URI. (default is 45 seconds), specify -timeout -1 to disable. -g, -genResolver generate an absolute-import resolver. -u, -useResolver specify an absolute-import resolver to use during parsing. -d, -deployScope indicates how to deploy the server. Valid arguments are: "Request", "Session", "Application".
Explanation: These are the options to WSDL2Java.
User Response: Use the specified options when invoking WSDL2Java.

WSWS3001I: Info: Extended Options: -U, -user login username to access the WSDL-URI. -P, -password login password to access the WSDL-URI. -a, -all generate java files for all types, even unreferenced ones. -z, -noDataBinding map all types (including base schema types) to SOAPElement. -t, -testCase emit template junit testcase class for testing Web service. -D, -Debug print debug information. -f, -fileNStoPkg file of NStoPkg mappings (default NStoPkg.properties). -j, -genJava generate Java files. Valid arguments are: "No" "IfNotExists" (default) "Overwrite" -s, -javaSearch when -genJava is set to "IfNotExists", determines how file existence is detected. Valid arguments are: "File" (default) "Classpath" "Both" -x, -genXML generate XML and XMI files. Valid arguments are: "No" "IfNotExists" (default) "Overwrite" -E, -genEquals Enable the hashcode/equal generation. Valid arguments are: "yes" "no" (default) -I, -genImplSer Have generated beans implement java.io.Serializable. Valid arguments are: "yes" "no" (default) -y, -noWrappedArrays Disable .NET wrapped array pattern. Generate beans containing arrays. -w, -noWrappedOperations Disable .NET wrapped operation pattern. Generate request and response beans.
Explanation: These are the extended options to WSDL2Java.
User Response: These are advanced options that users should not generally use.

WSWS3002I: Java2WSDL emitter Usage: Java2WSDL [options] class-of-portType Options: -location web service location url -output output WSDL file name -input input wsdl file name used to build wsdl from existing wsdl information -bindingTypes list of binding types to include in the wsdl file the default is "http" examples: -bindingTypes http,ejb -bindingTypes http,jms -style valid arguments: document (the default): generate document style wsdl rpc: generate rpc style wsdl -use valid arguments: literal (the default): literal use encoded: encoded use -transport This option has been deprecated. Use the -bindingTypes option instead. -portTypeName name of the portType defaults to name of the input class -bindingName name of the binding defaulted from portType if not specified -serviceElementName name of the service defaulted from portType name if not specified -servicePortName name of the port defaulted from -location if not specified -namespace target namespace of wsdl -PkgtoNS = mapping of package names to namespaces -implClass class that contains implementation of methods in class-of-portType. The debug information in the class is used to obtain the method parameter names, which are used to set the WSDL part names. -extraClasses other classes that should be added to the wsdl -classpath classpath to use for class introspection. -verbose display verbose messages -help displays this message -helpX displays extended options
Explanation: These are the options to Java2WSDL.
User Response: Use the specified options when invoking Java2WSDL.

WSWS3003I: Info: Extended Options: -wrapped indicate if wsdl should respect "wrapped" rules valid only for -style document and -use literal. the default is true. -stopClasses space or comma separated list of class names which will stop inheritance search when processing classes -methods space or comma separated list of method names from the SEI which are to be exposed in the output wsdl -soapAction valid arguments: OPERATION sets soapAction field to the operation name. NONE sets soapAction field to "". DEFAULT uses deployment information to set the field. -outputImpl specify if you want both interface and implementation wsdls -locationImport location of interface WSDL file -namespaceImpl target namespace for implementation WSDL -MIMEStyle valid arguments: AXIS: AXIS style MIME representation WSDL11 (default): WSDL 1.1 MIME representation swaRef: WS-I BP 1.1 representation (swaRef where appropriate) -propertiesFile filename of a properties file that contains a list of class names which should be added to the type section of the output wsdl. Example of file content: extraClasses=com.ibm.Class1,com.sun.Class2,org.apache.Class3 -voidReturn valid arguments: ONEWAY:treat methods with void returns as one-way TWOWAY:treat methods with void returns as two-way -debug display debug messages -properties sets binding-specific properties to be used by binding generators example: -properties prop1=value1,prop2=value2 Supported binding-specific properties:
Explanation: These are the extended options to Java2WSDL.
User Response: These are advanced options that users should not generally use.

WSWS3004W: Warning: The -location was not set, the value "{0}" is used instead.
Explanation: The -location option is a required option.
User Response: Please specify the -location option.

WSWS3005W: Warning: The -server-side option must have an argument that is Bean or EJB. Defaulting to Bean.
Explanation: The -server-side option is incorrect.
User Response: Please specify the correct -server-side option.

WSWS3006W: Warning: The argument of the -transport option must be "jms" or "http". The default setting ("http") will be used.
Explanation: The -transport option is incorrect.
User Response: Please specify the correct option.

WSWS3007E: Error: The {0} operation of {1} has an output element. This output element is removed and the operation is changed to one-way.
Explanation: This pre-existing operation has an output element. It is removed.
User Response: None.

WSWS3008E: Error: The {0} operation of {1} has a fault element. The faults are removed and the operation is changed to one-way.
Explanation: This pre-existing operation has a fault element. It is removed.
User Response: None.

WSWS3009I: Info: Loading Class {0}
Explanation: Loading specified class.
User Response: None.

WSWS3010I: Info: Generating {0} {1}
Explanation: Generating indicated construct.
User Response: None.

WSWS3011E: Invalid destination type "{0}" specified within a JMS endpoint URL.
Explanation: A JMS endpoint URL must specify either 'queue' or 'topic' as the destination type.
User Response: Correct the JMS endpoint URL and re-try.

WSWS3012E: Invalid property "{0}" encountered in JMS endpoint URL.
Explanation: A JMS endpoint URL string contained an unrecognized property.
User Response: Correct the JMS endpoint URL and re-try.

WSWS3013E: The JMS endpoint URL is missing one or more of the following required properties: connectionFactory, destination, targetService
Explanation: A JMS endpoint URL string must contain the following properties: connectionFactory, destination, targetService. These properties are used to describe the destination queue or topic and target service.
User Response: Correct the JMS endpoint URL and re-try.

WSWS3014E: Error creating InitialContext: {0}
Explanation: An error occurred while trying to create a JNDI InitialContext object.
User Response: Use the detailed information in the original error message to determine the problem.

WSWS3015E: Caught NamingException: {0}
Explanation: The specified error occurred during a JNDI 'lookup' operation.
User Response: Ensure that the JNDI name is correct.

WSWS3016E: Caught JMSException: {0}
Explanation: A JMS operation resulted in the specified JMSException.
User Response: Use the detailed information in the original error message to determine how to correct the problem.

WSWS3017E: Linked Exception: {0}
Explanation: None.
User Response: None.

WSWS3018E: Caught exception during request processing: {0}
Explanation: The specified exception occurred while a request was being processed.
User Response: Use the detailed information in the original error message to determine how to correct the problem.

WSWS3019E: Caught WebServicesFault: {0}
Explanation: The specified WebServicesFault exception occurred.
User Response: Use the detailed information in the original error message to determine how to correct the problem.

WSWS3020E: Error getting server engine.
Explanation: The Web services message-driven bean listener was unable to retrieve a configured server engine during its initialization.
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/.

WSWS3021E: The required "{0}" property was not present in the inbound JMS request message.
Explanation: The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic. This is an internal error.
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/.

WSWS3022E: Unrecognized inbound JMS request message type.
Explanation: The Web services JMS listener received a JMS message that was not a TextMessage or a BytesMessage. The JMS listener supports only these two JMS message types.
User Response: Ensure that the JMS sender uses the correct JMS message type.

WSWS3023E: Two-way requests are not supported for topic destinations.
Explanation: A two-way request/response was invoked for a topic destination, but only one-way requests are supported when using a topic.
User Response: Ensure that any services which use topic destinations contain only one-way operations. This means that within the WSDL file, the operation does not contain an 'output' message.

WSWS3024E: Root part containing SOAP envelope not found. contentId = {0}
Explanation: Internal Error.
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/.

WSWS3025E: Error: Could not locate a parameter named {0} for {1}.
Explanation: Suspect a bad mapping file supplied to WSDL2Java.
User Response: Correct your mapping file.

WSWS3026E: Error: The argument of the -voidReturn option must be "oneway" or "twoway".
Explanation: The -voidReturn option is incorrect.
User Response: Please specify the correct option.

WSWS3027E: Error: The {0} SAX event is not supported by SOAP.
Explanation: The message is not a legal SOAP message.
User Response: Contact party that sent this message.

WSWS3028E: Error: A _Helper class was not found for {0}.
Explanation: The _Helper class is needed for proper serialization or deserialization. Serialization or deserialization may fail.
User Response: Ensure that the _Helper class was properly emitted by WSDL2Java and deployed correctly.

WSWS3029W: Warning: The xml construct named {0} cannot be mapped to a java type. The construct will be mapped to javax.xml.soap.SOAPElement.
Explanation: Some xml constructs cannot be mapped to java types.
User Response: The application code will need to use the SOAPElement methods to construct and analyze the data.

WSWS3030E: Error: An internal error occurred while trying to locate the target method. Debug:{0}
Explanation: An internal error occurred. Possibly due to an error in the deployment information.
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/.

WSWS3031E: Error: Serialization cannot occur for {0}. There are no registered type mappings.
Explanation: The indicated object cannot be serialized.
User Response: Make sure that a proper serializer is registered.

WSWS3032I: Info: Attempt to get a secure socket factory using KeyStore: {0} and TrustStore: {1}, or Cryptographic token in: {2}
Explanation: Used either a KeyStore/TrustStore pair or a cryptographic token to get a secure socket factory
User Response: None.

WSWS3033E: Error: Deserialization cannot occur for {0}.
Explanation: The indicated type cannot be deserialized.
User Response: Make sure that a proper deserializer is registered.

WSWS3034E: Error: The OperationDesc for {0} was not matched to a method of {1}. Debug:{2}
Explanation: Internal error caused by improper startup code.
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/.

WSWS3035E: Error: {0}.{1} threw RuntimeException.
Explanation: Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original exception.
User Response: Correct Handler code to eliminate RuntimeException.

WSWS3036I: Replacing response message with SOAP Fault. Original Response Message: {0}
Explanation: Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original response message.
User Response: Correct Handler code to eliminate RuntimeException.

WSWS3037E: Error: Serialization cannot occur for {0}.
Explanation: The indicated object cannot be serialized.
User Response: Make sure that a proper serializer is registered.

WSWS3038E: Error: Deserialization cannot occur for {0}. There are no registered type mappings.
Explanation: The indicated type cannot be deserialized.
User Response: Make sure that a proper deserializer is registered.

WSWS3039E: Error: Resource has been deleted.
Explanation: Trying to access a deleted memory managed data source.
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/.

WSWS3040E: Error: Malformed arrayType value ''{0}''
Explanation: The arrayType attribute in the soap message is invalid.
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/.

WSWS3041E: Error: Bad authentication type (I can only handle "Basic").
Explanation: Only Basic authentication is supported with the SimpleServerEngine.
User Response: You should not be using the SimpleServerEngine.

WSWS3042E: Error: Invalid boolean (found {0}).
Explanation: A boolean value in a soap message must be '0', '1', 'true' or 'false'.
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/.

WSWS3043E: Error: Unexpected characters in a calendar value: {0}
Explanation: A calendar value in a soap message was invalid.
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/.

WSWS3044E: Error: Bad character or insufficient number of characters in hex string.
Explanation: A character in a hex string was invalid.
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/.

WSWS3045E: Error: Invalid date: {0}
Explanation: A bad date value was found in a soap message.
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/.

WSWS3046E: Error: Invalid date/time: {0}
Explanation: A bad date/time value was found in a soap message.
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/.

WSWS3047E: Error: Cannot deserialize element {1} of bean {0}.
Explanation: The specified bean does not have a property that matches the element. The soap message cannot be deserialized.
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/.

WSWS3048E: Error: Class ''{0}'' cannot be specified as a Handler class.
Explanation: An attempt was made to deploy the indicated class as a Handler class. However it does not extend the Handler class.
User Response: Correct your deployment information. CMSG0002

WSWS3049E: Error: A bad Holder class was encountered: {0}
Explanation: An attempt was made to use the specified class as a Holder. However the class does not extend the Holder interface.
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/.

WSWS3050E: Error: Explicit array length is not a valid integer ''{0}''.
Explanation: The soap message contains an array that has a non-integer array length. The soap message cannot be deserialized.
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/.

WSWS3051E: Error: No ''name'' attribute was specified in an undeployment element.
Explanation: This is normally the result of an internal error in the deployment software.
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/.

WSWS3052E: Error: Bad envelope namespace: {0}
Explanation: The envelope element of the soap message has an incorrect namespace. The message cannot be deserialized.
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/.

WSWS3053E: Error: An attempt was made to construct a Name object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3054E: Error: An attempt was made to construct a NCName object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3055E: Error: An attempt was made to construct a NegativeInteger object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3056E: Error: An attempt was made to construct a NMToken object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3057E: Error: An attempt was made to construct a NonNegativeInteger object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3058E: Error: An attempt was made to construct a NonPositiveInteger object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3059E: Error: Malformed offset attribute ''{0}''.
Explanation: The offset attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized.
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/.

WSWS3060E: Error: Invalid Parameter mode {0}.
Explanation: Internal exception of the WSDL2Java emitter.
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/.

WSWS3061E: Error: Malformed position attribute ''{0}''.
Explanation: The position attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized.
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/.

WSWS3062E: Error: portName should not be null.
Explanation: The portName argument to the service.getCalls method must be a recognized port name.
User Response: Ensure that the argument to the service.getCalls method is appropriate.

WSWS3063E: Error: An attempt was made to construct a PosInteger object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3064E: Error: Cannot handle non-GET, non-POST request.
Explanation: SimpleServerEngine does not understand the request.
User Response: Don't use the SimpleServerEngine.

WSWS3065E: Error: Unrecognized -scope: {0}. Ignoring it.
Explanation: The argument of the scope option must be Request, Application, or Session.
User Response: Use the proper -scope option when invoking WSDL2Java.

WSWS3066E: Error: Expected ''envelope'' but found {0}
Explanation: A soap message does not contain an envelope element.
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/.

WSWS3067E: Error: Invalid time: {0}
Explanation: A bad time value was found in a soap message.
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/.

WSWS3068E: Error: Invalid timezone: {0}
Explanation: A bad timezone was found in a soap message.
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/.

WSWS3069E: Error: Found languageSpecificType namespace ''{0}'', expected ''{1}''
Explanation: A problem has occurred in the deployment software.
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/.

WSWS3070E: Error: An attempt was made to construct an UnsignedByte object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3071E: Error: An attempt was made to construct an UnsignedShort object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3072E: Error: An attempt was made to construct an UnsignedInt object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3073E: Error: An attempt was made to construct an UnsignedLong object with an invalid string: {0}
Explanation: Normally this is caused by an invalid soap message.
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/.

WSWS3074E: Error: Cannot add a second body to a soap envelope.
Explanation: This error could be the result of an invalid soap message.
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/.

WSWS3075E: Error: User ''{0}'' not authenticated (unknown user).
Explanation: User cannot be authenticated.
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/.

WSWS3076E: Error: User ''{0}'' not authenticated.
Explanation: User cannot be authenticated.
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/.

WSWS3077E: Error: User ''{0}'' not authorized to ''{1}''
Explanation: User is not authorized.
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/.

WSWS3078E: Error: Cannot convert {0} to bytes.
Explanation: Internal Error: The soap message cannot be converted into bytes.
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/.

WSWS3079E: Error: Cannot convert form {0} to String.
Explanation: Internal Error: The soap message cannot be converted into a String.
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/.

WSWS3080E: Error: Could not convert {0} to bean field ''{1}'', type {2}
Explanation: The indicated value could not be assigned to the bean field. The soap message cannot be deserialized.
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/.

WSWS3081E: Error: Could not convert value to int.
Explanation: 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/.

WSWS3082E: Error: Cannot serialize null arrays.
Explanation: Internal Error.
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/.

WSWS3083E: Error: getURL failed to correctly process URL; protocol not supported.
Explanation: Tool option error. See other messages.
User Response: Fix the URL.

WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize.
Explanation: This message normally indicates that the soap message is invalid. The engine was expecting a simple value when it encountered a child element. The soap message cannot be deserialized.
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/.

WSWS3085E: Error: Cannot invoke Call with null namespace URI for method {0}
Explanation: Internal Error.
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/.

WSWS3086E: Error: Cannot serialize a {0} with the ArraySerializer.
Explanation: The indicated class cannot be serialized with the array serializer.
User Response: Suspect a problem with the deployment information.

WSWS3087E: Error: Cannot serialize non-Elements with an ElementSerializer.
Explanation: The element serializer can only be used to serialize org.w3c.dom.Element objects.
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/.

WSWS3088E: Error: Cannot serialize a raw object with the SimpleSerializer.
Explanation: The SimpleSerializer cannot be used to serialize a non-registered object.
User Response: Make sure your this class is registered with an appropriate type.

WSWS3089E: Error: Cannot set location URI: {0}
Explanation: Internal Error.
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/.

WSWS3090E: Error: Unable to tunnel through {0}:{1}. Proxy returns "{2}"
Explanation: Can't make the appropriate tunnel.
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/.

WSWS3091E: Error: Changing admin password.
Explanation: Changed passwords on AdminClient.
User Response: AdminClient is not fully supported.

WSWS3092E: Error: SOAPElement.setAlternateContent called when a child element is present.
Explanation: The SAAJ model is being used incorrectly. Please contact the Web services team. if this problem is occurring in the runtime.
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/.

WSWS3093E: Error: Could not create Call object in AdminClient.
Explanation: Internal Error.
User Response: Don't use AdminClient.

WSWS3094E: Error: WSDDPort couldn't construct provider!
Explanation: Internal Error with deployment software.
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/.

WSWS3095E: Error: Connection closed.
Explanation: The connection is closed. The remote service call cannot be made.
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/.

WSWS3096E: Error: Duplicate file name: {0}. Hint: you may have mapped two namespaces with elements of the same name to the same package name.
Explanation: WSDL2Java issues this message if an different qnames result in the creation of the same java file.
User Response: Fix your wsdl or use the NStoPkg options to differentiate the classes.

WSWS3097E: Error: Emitter failure. All input parts must be listed in the parameterOrder attribute of {0}
Explanation: The parameter order attribute in the wsdl is incorrect.
User Response: Fix your wsdl.

WSWS3098E: Error: Emitter failure. Cannot find endpoint address in port {0} in service {1}
Explanation: The endpoint address cannot be found.
User Response: Fix your wsdl.

WSWS3099E: Error: Emitter failure. Invalid endpoint address in port {0} in service {1}: {2}
Explanation: The endpoint address is invalid.
User Response: Fix your wsdl.

WSWS3100E: Error: Emitter failure. No binding found for port {0}
Explanation: Specify a binding on the service wsdl port.
User Response: Fix your wsdl

WSWS3101E: Error: Emitter failure. No binding entry found for {0}
Explanation: Internal Error.
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/.

WSWS3102E: Error: Emitter failure. No portType entry found for {0}
Explanation: Internal Error.
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/.

WSWS3103E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document. Hint: make sure is fully qualified.
Explanation: The binding must be defined if referenced.
User Response: Fix the WSDL.

WSWS3104E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document {1}. Hint: make sure is fully qualified.
Explanation: The binding must be defined if referenced.
User Response: Fix the WSDL.

WSWS3105E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document. Hint: make sure is fully qualified.
Explanation: The portType must be defined if referenced.
User Response: Fix the WSDL.

WSWS3106E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document {1}. Hint: make sure is fully qualified.
Explanation: The portType must be defined if referenced.
User Response: Fix the WSDL.

WSWS3107E: Error: Generic Error.
Explanation: 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/.

WSWS3108E: Error: Error: {0}
Explanation: 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/.

WSWS3109E: Error: Error invoking Web service operation: {0}
Explanation: Problem occurred invoking remote Web service.
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/.

WSWS3110E: Error: Error processing ''{0}''
Explanation: Admin error.
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/.

WSWS3111E: Error: Error determining if {0} already exists. Will not generate this file.
Explanation: Internal Error.
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/.

WSWS3112E: Error: Generating WebServicesFault due to missing SOAPAction.
Explanation: 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/.

WSWS3113E: Error: Cannot add a second header to a soap envelope.
Explanation: This error could be the result of an invalid soap message.
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/.

WSWS3114E: Error: Internal error.
Explanation: Internal Error.
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/.

WSWS3115E: Error: Configuration file directory ''{0}'' is not readable.
Explanation: The specified directory cannot be read.
User Response: Fix your configuration.

WSWS3116W: Warn: PERFORMANCE ALERT: The following message is re-parsed: {0}
Explanation: Non performant serialization encountered.
User Response: Examine code and make appropriate changes.

WSWS3117E: Error: Invalid container type (expected "ejb", "web", "client" or "none"), defaulting to "none".
Explanation: The -container option of WSDL2Java is wrong.
User Response: Fix the option setting.

WSWS3118E: Error: Invalid role (expected "develop-client", "deploy-client", "develop-server", or "deploy-server"), defaulting to "develop-client".
Explanation: The -role option of WSDL2Java is wrong.
User Response: Fix the option setting.

WSWS3119W: Warning: Invalid option combination: -role develop-server and -container client or -container none are invalid. The -container will be defaulted to "web".
Explanation: The Web service always runs in a web or ejb container.
User Response: Fix the options and rerun WSDL2Java.

WSWS3120E: Error: Configuration is missing.
Explanation: This is most likely due to a previous error with the Web services deployment descriptor.
User Response: Review the log for previous errors.

WSWS3121I: Info: {0} is a oneway operation.
Explanation: informational message.
User Response: no action required.

WSWS3122E: Error: Could not find service {0} referenced in URI {1}
Explanation: The specified service could not be found.
User Response: Check the name of the service specified by the client and the deployment of that service on the server.

WSWS3123E: Error: Javaclass {0} specified for handler {1} must implement {2} OR {3}. The handler will be skipped.
Explanation: A configuration file (was-webservices.xml) defines a handle javaclass that does not implement the expected interface.
User Response: Specify javaclass that implements the expected interface.

WSWS3124W: Warning: Invalid -genJava option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Explanation: The -genJava option of WSDL2Java is wrong.
User Response: Correct the option setting.

WSWS3125W: Warning: Invalid -genXML option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Explanation: The -genXML option of WSDL2Java is wrong.
User Response: Correct the option setting.

WSWS3126E: Error: Could not get a secure socket factory from the following SSL Configuration: {0}.
Explanation: Could not get a secure socket factory.
User Response: Correct your SSL configuration.

WSWS3127E: Error: Invalid WSDD element ''{0}'' (wanted ''{1}'').
Explanation: Error occurred during deployment. This is probably an internal error.
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/.

WSWS3128E: Error: Could not make envelope from bytes.
Explanation: This could possibly due to a deserialization error. Look for other errors.
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/.

WSWS3129E: Error: Only interfaces may be used for the proxy Class argument of the Service.getPort method.
Explanation: The getPort method requires a proxy interface.
User Response: Correct the invocation of the getPort method.

WSWS3130E: Error: Only interfaces which extend java.rmi.Remote may be used for the proxy Class argument of the Service.getPort method.
Explanation: The proxy Class argument must be an interface that extends java.rmi.Remote.
User Response: Fix the invocation of the getPort method.

WSWS3131E: Error: Must specify a password for AdminClient.
Explanation: A password must be supplied.
User Response: AdminClient is not fully supported.

WSWS3132E: Error: No target service was found.
Explanation: Internal Error.
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/.

WSWS3133E: Error: Need to specify a user for authorization.
Explanation: No user was found to authorize.
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/.

WSWS3134E: Error: Remote administrator access is not allowed.
Explanation: Cannot administer remotely.
User Response: The Admin class is not fully supported.

WSWS3135E: Error: Body not found.
Explanation: A body was expected in the soap envelope, but was not found. The soap message cannot be deserialized.
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/.

WSWS3136E: Error: No deserializer defined for array type {0}
Explanation: The array of the indicated component type could not be deserialized.
User Response: This problem may be due to invalid deployment information.

WSWS3137E: Error: No deserialization context to use in SOAPElement.convertToObject().
Explanation: Internal Error.
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/.

WSWS3138E: Error: No custom elements allowed at top level until after the tag.
Explanation: The soap message is invalid and cannot be deserialized.
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/.

WSWS3139E: Error: No deserializer for {0}
Explanation: Normally this is the result of bad client or server deployment information.
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/.

WSWS3140E: Error: Deserializing parameter ''{0}'': could not find deserializer for type {1}
Explanation: Nornally this is the result of a bad soap message or invalid server deployment information.
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/.

WSWS3141E: Error: Could not get DOM document: XML was "{0}"
Explanation: Internal Error.
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/.

WSWS3142E: Error: Could not find Web services engine.
Explanation: Probably an Internal Error.
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/.

WSWS3143W: Warning: Expected instance of ''EngineConfiguration'' in environment.
Explanation: Invalid configuration data.
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/.

WSWS3144E: Error: Cannot locate handler: {0}
Explanation: Internal Error with deployment information.
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/.

WSWS3145E: Error: No HandlerProvider ''handlerClass'' option was specified.
Explanation: Missing information in deployment information.
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/.

WSWS3146E: Error: No handlers in {0} ''{1}''
Explanation: Missing handlers in deployment information.
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/.

WSWS3147E: Error: no {0} header!
Explanation: Header missing in soap message.
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/.

WSWS3148E: Error: Processing instructions are not allowed within SOAP messages.
Explanation: The soap message is invalid and cannot be deserialized due to presences of processing instructions.
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/.

WSWS3149E: Error: {0}: {1} is not a map.
Explanation: The object cannot be serialized by the MapSerializer. This is probably the result of an internal deployment error.
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/.

WSWS3150E: Error: No provider type matches QName ''{0}''
Explanation: Deployment information is not complete. This is probably the result of an internal error.
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/.

WSWS3151E: Error: No operation name specified.
Explanation: Internal Error.
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/.

WSWS3152E: Error: Cannot find operation: {0} - none defined
Explanation: The WSDL does not define any operations in the portType.
User Response: This is an internal error or deployment error.

WSWS3153E: Error: Cannot find operation: {0}
Explanation: The WDSL binding did not specify the operation.
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/.

WSWS3154E: Error: No ''{0}'' option was configured for the service ''{1}''
Explanation: The indicated option was not 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/.

WSWS3155E: Error: {0} not found as an input part OR an output part.
Explanation: The parameter order attribute must reference a message part.
User Response: Correct the WSDL.

WSWS3156E: Error: Cannot find port: {0}
Explanation: The specified port could not be found by Service.getPort.
User Response: Correct the invocation of Service.getPort.

WSWS3157E: Error: Cannot find portType: {0}
Explanation: The deployed wsdl is missing the portType.
User Response: Correct the deployed wsdl.

WSWS3158E: Error: No request message in MessageContext?
Explanation: Internal Error.
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/.

WSWS3159E: Error: No serializer found for class {0} in registry {1}
Explanation: Usually this indicates a internal error with the deployment information.
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/.

WSWS3160E: Error: Cannot find service: {0}
Explanation: Internal Error.
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/.

WSWS3161E: Error: No service has been defined.
Explanation: Internal Error.
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/.

WSWS3162E: Error: No service object defined for this Call object.
Explanation: Internal Error.
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/.

WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is {0}
Explanation: Internal Error. Suspect that the JavaBean's SoapBindingImpl class has been hot swapped.
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/.

WSWS3164E: Error: No security provider in MessageContext.
Explanation: Make sure a security provider is configured.
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/.

WSWS3165E: Error: No HTTP SOAPAction property in context.
Explanation: Internal Error.
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/.

WSWS3166E: Error: No client transport named ''{0}'' found.
Explanation: Internal Error.
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/.

WSWS3167E: Error: No transport mapping for protocol: {0}
Explanation: Internal Error.
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/.

WSWS3168E: Error: No mapped schema type for {0}
Explanation: The indicated array component type cannot be serialized. Make sure this type is 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/.

WSWS3169E: Error: Component requires a type attribute.
Explanation: The component of the vector cannot be deserialized.
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/.

WSWS3170E: Error: Must include type attribute for Handler deployment!
Explanation: Missing deployment information.
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/.

WSWS3171E: Error: No type QName for mapping!
Explanation: Missing deployment information in the type mapping registry.
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/.

WSWS3172E: Error: User ''{0}'' not authorized to ''{1}''
Explanation: 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/.

WSWS3173E: Error: Did not understand "MustUnderstand" header(s):{0}
Explanation: Handler did not understand mustUnderstand headers.
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/.

WSWS3174E: Error: No value field for RPCParam to use. {0}
Explanation: Internal Exception.
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/.

WSWS3175E: Error: {0} is null.
Explanation: Processing cannot continue because the indicated item is null.
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/.

WSWS3176E: Error: AdminClient did not initialize correctly: ''call'' is null!
Explanation: Internal Error.
User Response: AdminClient is not fully supported.

WSWS3177E: Error: Null namespace URI specified.
Explanation: Namespace argument must be specified.
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/.

WSWS3178E: Error: null parent.
Explanation: Tried to call SAAJ setParent with a null argument. This may be the result of an internal error.
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/.

WSWS3179E: Error: Null provider type passed to WSDDProvider.
Explanation: Missing deployment information. This may be the result of an internal error.
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/.

WSWS3180E: Error: Null response message.
Explanation: Internal Error.
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/.

WSWS3181E: Error: Odd number of digits in hex string.
Explanation: The HexBinary object cannot be constructed.
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/.

WSWS3182E: Error: Only one Body element allowed in SOAPEnvelope.
Explanation: The soap message contains multiple soap bodies inside the envelope. The soap message cannot be deserialized.
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/.

WSWS3183E: Error: Only one Header element allowed in SOAPEnvelope.
Explanation: The soap message contains multiple soap headers inside the envelope. The soap message cannot be deserialized.
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/.

WSWS3184E: Error: Number of parameters passed in ({0}) doesn''t match the number of IN/INOUT parameters ({1}) from the addParameter() calls.
Explanation: The number of parameters does not match the expected number of parameters.
User Response: This could be a DII or internal error.

WSWS3185I: Info: Parsing XML file: {0}
Explanation: informational message.
User Response: no action required.

WSWS3186E: Error: Error in parsing: {0}
Explanation: Problem occurred deserializing the soap message.
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/.

WSWS3187E: Error: Processing file {0}
Explanation: AdminClient error processing the indicated file.
User Response: AdminClient is not fully supported.

WSWS3188I: Info: {0} quitting.
Explanation: informational message.
User Response: no action required.

WSWS3189E: Error: Administration service requested to quit, quitting.
Explanation: Admin quitting.
User Response: Admin class is not fully supported.

WSWS3190E: Error: Unable to bind to port {0}. Did not start SimpleServerEngine.
Explanation: Internal Error.
User Response: SimpleServerEngine not fully supported.

WSWS3191I: Info: Configuration file read-only so engine configuration changes will not be saved.
Explanation: informational message.
User Response: no action required.

WSWS3192E: Error: return code: {0} {1}.
Explanation: 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/.

WSWS3193E: Error: Problem with servlet engine /WEB-INF directory
Explanation: /WEB-INF may not be accessible.
User Response: Correct problem with WEB-INF directory.

WSWS3194E: Error: Problem with servlet engine config file: {0}
Explanation: config file may not be accessible.
User Response: Correct problem with servlet engine config file.

WSWS3195W: Warn: Unable to load/create servlet engine config file, attempting internal default (from jar).
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: no action required.

WSWS3196E: Error: Problem with servlet engine config file (loading from jar).
Explanation: Configuration error.
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/.

WSWS3197I: Info: {0} starting up on port {1}.
Explanation: informational message.
User Response: no action required.

WSWS3198E: Error: Type/Element attribute on Part ''{0}'' is not set.
Explanation: The WSDL part must specify the type or element attribute.
User Response: Correct the deployed wsdl.

WSWS3199E: Error: Unexpected end of stream.
Explanation: Internal Error or problem with input soap message.
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/.

WSWS3200E: Error: Unknown host - could not verify administrator access.
Explanation: Unknown host encountered by Admin tool.
User Response: The Admin tool is not fully supported.

WSWS3201E: Error: Where {0} looks like:
Explanation: Admin tool error.
User Response: Admin tool is not fully supported.

WSWS3202E: Error: Error processing WSDL document: {0} {1}
Explanation: Normally an error with the deployed wsdl detected during service creation.
User Response: Correct the deployed wsdl.

WSWS3203E: Error: Missing WSDL document in Service.getPort.
Explanation: A WSDL document is needed if you want to use Service.getPort.
User Response: Correct your deployment information.

WSWS3204E: Error: {0} already exists.
Explanation: Internal Error in the WSDL2Java SymbolTable.
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/.

WSWS3205E: Error: Type {0} is referenced but not defined.
Explanation: Your wsdl references types or elements that are not defined.
User Response: Correct your wsdl.

WSWS3206E: Error: Cannot find EJB at JNDI location {0}
Explanation: There may be a problem with your JNDI configuration.
User Response: Correct your JNDI configuration.

WSWS3207E: Error: Cannot create InitialContext.
Explanation: An InitialContext was not created.
User Response: Inspect other errors to determine why InitialContext was not created.

WSWS3208E: Error: The definition of {0} results in a loop.
Explanation: Found recursive definition of the indicated type or element.
User Response: Correct your wsdl.

WSWS3209E: Error: Bad property. The value for {0} should be of type {1}, but it is of type {2}.
Explanation: A bad property detected on the Call or MessageContext. This could be caused by an internal error.
User Response: Fix the property.

WSWS3210E: Error: Null property name specified.
Explanation: A bad property was detected. This could be caused by an internal error.
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/.

WSWS3211E: Error: Null property value specified.
Explanation: A null property value was specified. This could be caused by an internal error.
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/.

WSWS3212E: Error: Property name {0} not supported.
Explanation: An unsupported property is being used.
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/.

WSWS3213E: Error: Null getter method specified.
Explanation: This is normally due to an internal error associated with the serialization engine.
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/.

WSWS3214E: Error: Null setter method specified.
Explanation: This is normally due to an internal error associated with the deserialization engine.
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/.

WSWS3215E: Error: Null public instance field specified.
Explanation: This is normally due to an internal error with the serialization engine.
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/.

WSWS3216E: Error: Null java class specified in TypeMappingImpl.isRegistered method.
Explanation: The isRegistered method requires a non-null java class. This error could be the result of an internal problem.
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/.

WSWS3217E: Error: Null qualified name specified in TypeMappingImpl.isRegistered method.
Explanation: The isRegistered method requires a non-null qname. This error could be the result of an internal problem.
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/.

WSWS3218E: Error: Null serializer factory specified in the TypeMappingImpl.register method.
Explanation: This error normally suggests a problem with the deployment software.
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/.

WSWS3219E: Error: Error: Message part {0} of operation or fault {1} is specified as a type and the soap:body use of binding "{2}" is literal. This WSDL is not currently supported.
Explanation: The WSDL contains unsupported MIME constructs.
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/.

WSWS3220E: Error: Error: Empty or missing service name.
Explanation: The WSDL service name is wrong.
User Response: Correct the WSDL.

WSWS3221E: Error: Bean attribute {0} is of type {1}, which is not a simple type.
Explanation: Attributes must be simple types.
User Response: Correct the WSDL.

WSWS3222E: Error: Attribute is of type {0}, which is not a simple type.
Explanation: Attributes must be simple types.
User Response: Correct the WSDL.

WSWS3223E: Error: Exception caught while constructing handler {0}: {1}
Explanation: Problem creating JAXRPC Handler.
User Response: Review reasons for thrown exception.

WSWS3224I: Info: No disk access, using memory only.
Explanation: informational message
User Response: No action required.

WSWS3225E: Error: No DeserializerFactory for {0}
Explanation: This normally indicates a problem with the deployed type mapping registry.
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/.

WSWS3226E: Error: Null FieldDesc specified.
Explanation: Internal Exception.
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/.

WSWS3227E: Error: Exception:
Explanation: Used for various exceptions. See other messages.
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/.

WSWS3228E: Error: Exception: {0}
Explanation: Used for various exceptions.. See other messages.
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/.

WSWS3229E: Error: ConfigurationException:
Explanation: Normally indicates an internal error has occurred.
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/.

WSWS3230E: Error: ParserConfigurationException:
Explanation: Indicates that an error has occurred while configuring the xml parser.
User Response: Correct the parser configuration.

WSWS3231E: Error: SAXException:
Explanation: Indicates that a SAX Exception has occurred. Normally the exception is due to a problem configuring the parser.
User Response: Correct the parser configuration.

WSWS3232E: Error: java.net.UnknownHostException:
Explanation: Normally indicates that an internal error has occurred.
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/.

WSWS3233E: Error: javax.mail.MessagingException:
Explanation: Normally indicates a problem with a MIME message.
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/.

WSWS3234E: Error: java.io.IOException:
Explanation: Normally an internal error.
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/.

WSWS3235E: Error: java.io.IOException: {0}
Explanation: Normally an internal error.
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/.

WSWS3236E: Error: IllegalAccessException:
Explanation: Normally an internal error.
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/.

WSWS3237E: Error: IllegalArgumentException:
Explanation: This may be issued during overloaded message processing.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3238E: Error: IllegalArgumentException: {0}
Explanation: This error may occur during overloaded method processing.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3239E: Error: InvocationTargetException:
Explanation: A problem occurred invoking the indicated target.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3240E: Error: InstantiationException:
Explanation: This error may indicate a problem with MIME attachments.
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/.

WSWS3241E: Error: MalformedURLException:
Explanation: Malformed URL Exception occurred in the SimpleServerEngine.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3242E: Error: WebServicesFault:
Explanation: A WebServicesFault has occurred.
User Response: See other messages for more detailed information.

WSWS3243I: Info: Mapping Exception to WebServicesFault.
Explanation: informational message. See other messages for details about why the fault was issued.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3244I: Info: Mapping Exception to WebServicesFault: {0}
Explanation: informational message. See other messages for details about why the fault was issued.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3245E: Error: WSDL2Java emitter timed out (this often means the WSDL at the specified URL is inaccessible)!
Explanation: Normally indicates that the WSDL is not accessible.
User Response: Make sure the WSDL is accessible.

WSWS3246E: Error: SOAPFault.addDetail called when a detail is present.
Explanation: Internal Error.
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/.

WSWS3247E: Error: No endpoint.
Explanation: See other messages for more details.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3248E: Error: Unsupported attachment type "{0}" only supporting "{1}".
Explanation: Indicates that an unsupported attachment type was encountered.
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/.

WSWS3249E: Error: This attachment implementation accepts only SOAPPart objects as the root part.
Explanation: Internal Error.
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/.

WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.
Explanation: Possibly an internal error.
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/.

WSWS3251E: Error: Stream closed.
Explanation: Tried to access a closed stream.
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/.

WSWS3252E: Error: End of stream encountered before final boundary marker.
Explanation: Internal Error.
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/.

WSWS3253E: Error: maxCached value is bad: {0}
Explanation: Internal Error.
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/.

WSWS3254E: Error: Reset and mark not supported!
Explanation: Internal Error.
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/.

WSWS3255E: Error: input buffer is null.
Explanation: Internal Error
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/.

WSWS3256E: Error: Offset is negative: {0}
Explanation: Internal Error.
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/.

WSWS3257E: Error: Length: {0}
Explanation: Internal Error.
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/.

WSWS3258E: Error: Write beyond buffer.
Explanation: Internal Error.
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/.

WSWS3259E: Error: Error reading data stream: {0}
Explanation: Internal Error.
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/.

WSWS3260E: Error: File for data handler does not exist: {0}
Explanation: Internal Error.
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/.

WSWS3261E: Error: Error in MIME data stream, start boundary not found, expected: {0}.
Explanation: Internal Error.
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/.

WSWS3262E: Error: Error in parsing mime data stream: {0}.
Explanation: Internal Error.
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/.

WSWS3263E: Error: No support for attachments.
Explanation: Internal Error.
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/.

WSWS3264E: Error: No content.
Explanation: Data Handler has no content.
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/.

WSWS3265E: Error: No engine configuration file - aborting.
Explanation: Possibly an internal error.
User Response: Make sure your engine configuration is correct.

WSWS3266E: Error: The element "{0}" is an attachment with sub elements which is not supported.
Explanation: Child elements were not anticipated in the soap message. The soap message cannot be deserialized.
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/.

WSWS3267E: Error: Error: Missing type resolution for element {2}, in WSDL message part {0} of operation {1}.
Explanation: Your WSDL may be bad.
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/.

WSWS3268E: Error: The soap:operation for binding operation {0} must have a "use" attribute.
Explanation: Probably an internal error.
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/.

WSWS3269E: Error: Default type mapping cannot be modified.
Explanation: The type mapping cannot be modified after registration has occurred.
User Response: Please correct your code.

WSWS3270E: Error: Type mapping cannot be modified via delegate.
Explanation: Internal Error.
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/.

WSWS3271E: Error: Invalid TypeMapping specified: wrong type or null.
Explanation: Invalid TypeMapping registration.
User Response: Please correct your code.

WSWS3272E: Error: Default type mapping from secondary type mapping registry is already in use.
Explanation: Cannot change default type mapping after registration.
User Response: Please correct your code.

WSWS3273E: Error: There is no stub implementation for the interface:
Explanation: You cannot call this getPort method because there is no stub implementation of the interface.
User Response: Please change your code.

WSWS3274E: Error: {0}: {1} is not a vector.
Explanation: Internal Error.
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/.

WSWS3275E: Error: Invalid parameter mode byte ({0}) passed to getModeAsString().
Explanation: Internal Error.
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/.

WSWS3276E: Error: Marking streams not supported.
Explanation: Internal Error.
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/.

WSWS3277E: Error: Could not resolve to an operation. The message contains an element named ""{0}"", but this does not match any operation of the target port. Debug: {1}
Explanation: This may be a symptom of a Web service deployment problem or an incorrect SOAP request message.
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/.

WSWS3278E: Error: Attempt to set implementation class on a ServiceDesc which has already been configured.
Explanation: Internal Exception.
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/.

WSWS3279E: Error: Unable to create JavaBean of type {0}. Missing default constructor? Error was: {1}.
Explanation: Make sure that the JavaBean has a default constructor.
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/.

WSWS3280E: Error: The value of -soapAction must be DEFAULT, NONE or OPERATION.
Explanation: A bad argument was specified for -soapAction.
User Response: Use the correct Java2WSDL -soapAction option.

WSWS3281E: Error: Tried to invoke method ''{0}'' with argument classes ''{1}'' against object ''{2}'' of class ''{3}''. The arguments do not match the signature.
Explanation: Suspect a problem with the Web service deployment, with the soap message, or hot swapping of the service's SoapBindingImpl class.
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/.

WSWS3282I: Info: Generating {0}.
Explanation: Informational message indicating which java classes are generated by WSDL2Java.
User Response: no action required.

WSWS3283E: Error: The value of -style must be DOCUMENT or RPC.
Explanation: The -style option of Java2WSDL is incorrect.
User Response: Use a correct -style option.

WSWS3284E: Error: Could not find class ''{0}'' for the service.
Explanation: Suspect a Web service deployment error.
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/.

WSWS3285E: Error: Could not find class ''{0}'' for the service ''{1}''.
Explanation: Suspect a Web service deployment error.
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/.

WSWS3286E: Error: The has already been specified as, {0}. It cannot be specified again as {1}.
Explanation: Only one class file may be specified for Java2WSDL.
User Response: Correct your invocation of Java2WSDL.

WSWS3287E: Error: The was not specified.
Explanation: A class file must be specified for Java2WSDL.
User Response: Correct your invocation of Java2WSDL.

WSWS3288E: Error: The wsdl URI has already been specified as, {0}. It cannot be specified again as {1}.
Explanation: The WSDL file can only be specified once for WSDL2Java.
User Response: Correct your invocation of WSDL2Java.

WSWS3289E: Error: The wsdl URI was not specified.
Explanation: The WSDL URI must be specified for WSDL2Java.
User Response: Correct your invocation of WSDL2Java.

WSWS3290E: Error: Unrecognized {0}: ''{1}''
Explanation: Inappropriate value for the enumeration.
User Response: Please correct your code.

WSWS3291E: Error: The class {0} is not a bean class and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
Explanation: Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response: All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.

WSWS3292W: Warning: The class {0} is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
Explanation: Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response: All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.

WSWS3293E: Error: The class {0} does not contain a default constructor, which is a requirement for a bean class. The class cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
Explanation: Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response: All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.

WSWS3294E: Error: The XML Schema type ''{0}'' is not currently supported.
Explanation: WSDL2Java does not support this XML Schema type.
User Response: Correct your wsdl.

WSWS3295E: Error: Message part {0} of operation or fault {1} has no element or type attribute.
Explanation: Each message part must have an element or type attribute which locates the schema element/type.
User Response: Correct your wsdl.

WSWS3296E: Error: The value of {0} for attachment format must be {1};
Explanation: Internal Error.
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/.

WSWS3297E: Error: DIME Type length is {0} which exceeds maximum {0}
Explanation: Internal Error.
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/.

WSWS3298E: Error: DIME ID length is {0} which exceeds maximum {1}.
Explanation: Internal Error
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/.

WSWS3299E: Error: Max chunk size "{0}" needs to be greater than one.
Explanation: Internal Error.
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/.

WSWS3300E: Error: Max chunk size "{0}" exceeds 32 bits.
Explanation: Internal Error.
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/.

WSWS3301E: Error: Each DIME Stream must be read fully or closed in succession.
Explanation: Internal Error.
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/.

WSWS3302E: Error: DIME stream data not padded correctly.
Explanation: Internal Error.
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/.

WSWS3303E: Error: Received "{0}" bytes to read.
Explanation: Internal Error.
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/.

WSWS3304E: Error: Received "{0}" as an offset.
Explanation: Internal Error.
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/.

WSWS3305E: Error: Array to read is null.
Explanation: Internal Error.
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/.

WSWS3306E: Error: Array size of {0} to read {1} at offset {2} is too small.
Explanation: Internal Error.
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/.

WSWS3307E: Error: End of physical stream detected when more DIME chunks expected.
Explanation: Internal Error
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/.

WSWS3308E: Error: End of physical stream detected when {0} more bytes expected.
Explanation: Internal Error.
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/.

WSWS3309E: Error: There are no more DIME chunks expected!
Explanation: Internal Error.
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/.

WSWS3310E: Error: DIME header less than {0} bytes.
Explanation: Internal Error.
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/.

WSWS3311E: Error: DIME version received "{0}" greater than current supported version "{1}".
Explanation: Internal Error.
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/.

WSWS3312E: Error: DIME option length "{0}" is greater stream length.
Explanation: Internal Error.
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/.

WSWS3313E: Error: DIME stream closed during options padding.
Explanation: Internal Error.
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/.

WSWS3314E: Error: DIME stream closed getting ID length.
Explanation: Internal Error.
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/.

WSWS3315E: Error: DIME stream closed getting ID padding.
Explanation: Internal Error.
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/.

WSWS3316E: Error: DIME stream closed getting type.
Explanation: Internal Error.
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/.

WSWS3317E: Error: DIME stream closed getting type padding.
Explanation: Internal Error.
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/.

WSWS3318E: Error: DIME stream received bad type "{0}".
Explanation: Internal Error.
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/.

WSWS3319E: Error: A holder could not be found or constructed for the OUT parameter {0} of method {1}.
Explanation: Suspect a problem with deploying this Web service.
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/.

WSWS3320E: Error: Illegal argument passed to ParameterDesc.setJavaType. The java type {0} does not match the mode {1}.
Explanation: Suspect a problem with deploying this Web service. Probably an internal error.
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/.

WSWS3321E: Error: Invalid normalizedString value.
Explanation: The NormalizedString object could not be set due to an invalid value.
User Response: Correct the normalizedString value.

WSWS3322E: Error: Invalid token value.
Explanation: The Token object could not be set due to an invalid value.
User Response: Correct the token value.

WSWS3323E: Internal Error occurred while build the property descriptors for {0}.
Explanation: Internal Error.
User Response: Make sure the indicate class complies with JAX-RPC.

WSWS3324E: Error: Problems encountered trying to write schema for {0}
Explanation: Could not write the schema for the indicated class. This is probably due to an internal error.
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/.

WSWS3325E: Error: Error looking for parameter names in bytecode: input does not appear to be a valid class file.
Explanation: You probably specified an invalid class to Java2WSDL.
User Response: Correct the indicated class.

WSWS3326E: Error: Error looking for parameter names in bytecode: unexpected end of file.
Explanation: Internal Error.
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/.

WSWS3327E: Error: Error looking for parameter names in bytecode: unexpected bytes in file.
Explanation: Internal Error.
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/.

WSWS3328E: Error: The class {0} extends non-bean class {1}. An xml schema anyType will be used to define {0} in the wsdl file.
Explanation: Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
User Response: All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.

WSWS3329E: Error: The XML Schema type ''{0}'' is not valid in the Schema version ''{1}''.
Explanation: WSDL2Java error.
User Response: Please correct your wsdl.

WSWS3330I: Info: {0} already exists, WSDL2Java will not overwrite it.
Explanation: WSDL2Java informational message.
User Response: No action required.

WSWS3331E: Error: Invalid gYearMonth: {0}
Explanation: Error occurred while constructing a YearMonth object.
User Response: Use a correct value.

WSWS3332E: Error: Invalid gYear: {0}
Explanation: Error occurred while constructing a Year object.
User Response: Use a correct value.

WSWS3333E: Error: Invalid gMonth: {0}
Explanation: Error occurred while constructing a Month object.
User Response: Use a correct value.

WSWS3334E: Error: Invalid gDay: {0}
Explanation: Error occurred while constructing a Day object.
User Response: Use a correct value.

WSWS3335E: Error: Invalid gMonthDay: {0}
Explanation: Error occurred while constructing a MonthDay object.
User Response: Use a correct value.

WSWS3336E: Error: Invalid duration: must contain a P.
Explanation: Error occurred while constructing a Duration object.
User Response: Use a correct value.

WSWS3337E: Error: Serializer class {0} does not implement SimpleValueSerializer, which is necessary for attributes.
Explanation: This serializer cannot be used to serialize attributes.
User Response: Please correct your deployed type mappings.

WSWS3338E: Error: JIMI is necessary to use java.awt.Image attachments (http://java.sun.com/products/jimi/).
Explanation: Internal Error.
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/.

WSWS3339E: Error: javax.xml.transform.Source implementation not supported: {0}.
Explanation: An attempt was made to use the SourceDataHandlerSerializer to serialize a non-SourceStream object.
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/.

WSWS3340E: Error: The OperationDesc for {0} was not synchronized to a method of {1}.
Explanation: Internal Error. This error usually indicates that information was missing in the PortDesc/WSDDPort in regards to the definition of the Web service operations. The engine attempts to deduce the missing information, which may result in this particular error.
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/.

WSWS3341E: Error: No service class was found.
Explanation: Internal Error.
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/.

WSWS3342E: Error: Cannot handle {0}, can only handle JPEG image types.
Explanation: Internal Error.
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/.

WSWS3343W: Warning: Factory {0} Ignored: missing required method: {1}.
Explanation: Correct your factory implementation.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3344W: Warning: Factory {0} Ignored: invoke method failed: {1}.
Explanation: Invoke method failed.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3345E: Error: Unable to locate a valid EngineConfigurationFactory.
Explanation: Missing factory implementation.
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/.

WSWS3346E: Error: Factory {0} Ignored: unable to load/resolve class.
Explanation: Cannot load the indicated factory.
User Response: Make sure that the factory can be loaded.

WSWS3347E: Error: classname attribute is missing.
Explanation: WSDD Deployment information is missing. This may be due to an internal error.
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/.

WSWS3348E: Error: qname attribute is missing.
Explanation: WSDD Deployment information is missing. This may be due to an internal error.
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/.

WSWS3349E: Error: Element {0} is referenced but not defined.
Explanation: WSDL2Java error indicating that an element is referenced but no definition was found.
User Response: Please correct your wsdl.

WSWS3350E: Error: Missing type or ref attribute for node ''{0}''
Explanation: A type or ref attribute is used to reference a type or element.
User Response: Please correct your wsdl.

WSWS3351E: Error: Unable to deploy typemapping: {0}
Explanation: This may be due to a deployment problems.
User Response: Make sure that the indicated class can be found and loaded.

WSWS3352E: Error: Couldn''t find a matching Java operation for WSDD operation "{0}" ({1} args).
Explanation: Normally this indicates a problem with the missing or incorrect deployment information.
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/.

WSWS3353E: Error: Method style for message-based service wasn't one we recognized.
Explanation: Internal Error. This is an unsupported api.
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/.

WSWS3354E: Error: Method ''{0}'' does not match any of the valid signatures for message-style service methods.
Explanation: Internal Error. This is an unsupported api.
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/.

WSWS3355E: Error: unmatchedOp=Binding operation has no corresponding portType operation: name = {0}, input name = {1}, output name = {2}
Explanation: An invalid binding operation was encountered in the wsdl.
User Response: Please correct the wsdl.

WSWS3356E: Error: Couldn't find an appropriate operation for XML QName {0}
Explanation: Internal Error.
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/.

WSWS3357E: Error: while trying to deserialize operation {0}, an element named {1} was encountered. However, this element does not match any of the expected parameters for this operation. Here is the list of expected parameters: {2}
Explanation: The SOAP request message received by the service does not match the WSDL definition.
User Response: Make sure that the SOAP message sent to the service matches the WSDL definition.

WSWS3358E: Error: ERROR: Unable to match binding fault "{0}" from binding {2}, operation "{1}", to a PortType fault.
Explanation: The binding fault must have a corresponding portType fault.
User Response: Please correct the wsdl

WSWS3359E: Error: Fault is missing a name= attribute in operation "{0}", in binding {1}.
Explanation: The binding fault must have a name.
User Response: Please correct the wsdl.

WSWS3360E: Error: ERROR: Missing element inFault "{0}" in operation "{1}", in binding {2}
Explanation: The binding fault must have an appropriate element.
User Response: Please correct the wsdl.

WSWS3361E: Error: Found instance data for {0} in the soap:body instead of the soap:header.
Explanation: The soap message is incorrect.
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/.

WSWS3362E: Error: Didn''t find specified return QName {0}
Explanation: The response soap message is incorrect.
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/.

WSWS3363E: Error: The value of the -use option must be LITERAL or ENCODED.
Explanation: The -use option of Java2WSDL is incorrect.
User Response: Correct the -use option.

WSWS3364E: Error: Invalid class provided for -extraClasses option: {0}
Explanation: The -extraClasses option of Java2WSDL is incorrect.
User Response: Correct the -extraClasses option.

WSWS3365E: Error: Cannot invoke a oneway call when the call has a return type.
Explanation: A method was encountered that has a return type, but Java2WSDL was invoked in a mode that assumes that the method is one way.
User Response: Correct the class.

WSWS3366E: Error: The operation must be specified.
Explanation: Probably an internal error.
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/.

WSWS3367E: Error: Failure priming the MessageContext object for operation invocation: {0}
Explanation: Probably an internal error.
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/.

WSWS3368E: Error: The deserialization event {0} for ({1}) was unexpected in {2}.
Explanation: This can be caused by an internal error or a bad input soap message.
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/.

WSWS3369E: Error: The builder {0} does not have a SOAPElement to build.
Explanation: Internal Error.
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/.

WSWS3370E: Error: Only one SOAPEnvelope is allowed in a SOAPFactory.
Explanation: Internal Error.
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/.

WSWS3371E: Error: Cannot invoke addChildElement on a {0} object.
Explanation: Cannot add a child SOAPElement to the indicated object.
User Response: Correct your code.

WSWS3372E: Error: Cannot add a {0} child element to a {1} object.
Explanation: Cannot add the indicated child element.
User Response: Correct your code.

WSWS3373E: Error: Cannot invoke addTextNode on a {0} object.
Explanation: Cannot add a Text node to the indicated object.
User Response: Correct your code.

WSWS3374E: Error: Cannot replace SOAPElement's attributes.
Explanation: Cannot call setAttributes after the SOAPElement has attributes.
User Response: Correct your code.

WSWS3375E: Error: Cannot replace SOAPElement's MappingScope.
Explanation: Cannot call setMappingScope after the SOAPElement has a MappingScope.
User Response: Correct your code.

WSWS3376E: Error: Don't know how to convert alternate content of class {0}.
Explanation: This is an unrecognized alternate content type.
User Response: Correct your code.

WSWS3377E: Error: Multiple elements have the name ({0}):{1}.
Explanation: Expecting only one child element of the given qname.
User Response: Correct your code.

WSWS3378E: Error: Can't set alternate content on a SOAPElement that already has alternate content.
Explanation: An attempt was made to set alternate content on a SOAPElement that already has alternate content.
User Response: Make sure you remove the existing alternate content before replacing it.

WSWS3379E: Error: Prefix {0} is undefined.
Explanation: The indicated prefix does not have a corresponding namespace uri.
User Response: Correct your code or soap message.

WSWS3380E: Error: An attempt was made to modify a read-only MappingScope.
Explanation: Internal Error.
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/.

WSWS3381E: Error: Circular loop encountered while processing MappingScope.
Explanation: Internal Error.
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/.

WSWS3382E: Error: An unqualified namespace cannot have a prefix. Prefix is {0}.
Explanation: Internal Error.
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/.

WSWS3383E: Error: Illegal use of xmlns prefix encountered: {0}
Explanation: The soap message has an illegal xmlns prefix.
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/.

WSWS3384E: Error: Admin process failed.
Explanation: Admin tool failed.
User Response: The Admin tool is not fully supported.

WSWS3385E: Error: The onStartChild method of {0} did not return a processor.
Explanation: Internal Error.
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/.

WSWS3386E: Error: Tried to push a null processor.
Explanation: Internal Error.
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/.

WSWS3387E: Error: An attempt was made to serialize a null object. This should have been handled in the serialize() method.
Explanation: Internal Error.
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/.

WSWS3388E: Error: Exception generated while rewinding request handlers during fault processing: exception ignored, processing halted.
Explanation: An exception was thrown during handler fault processing.
User Response: Inspect your handlers.

WSWS3389E: Error: JAXRPC Handler Class {0} not found/loaded, ignored.
Explanation: The indicated class could not be found and/or loaded.
User Response: Determine why the class was not found or loaded.

WSWS3390E: Error: Load of class {0} failed unexpectedly.
Explanation: Internal Error.
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/.

WSWS3391W: Warn: {0}.handleRequest returned false and failed to set response message.
Explanation: Warning.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3392E: Error: Unexpected: Unable to create response message on behalf of handler.
Explanation: Warning.
User Response: This exception is unexpected. The cause is not immediately known.

WSWS3393E: Error: {0}.handlerRequest should not throw javax.xml.rpc.soap.SOAPFaultException on client-side.
Explanation: Internal Error.
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/.

WSWS3394E: Internal Error: attempted to put {0} into pool of {1}.
Explanation: Internal Error.
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/.

WSWS3395E: Error: {0}.{1} threw RuntimeException.
Explanation: Internal Error.
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/.

WSWS3396E: Error: Handler {0}: Protected state violation. (JSR 109, Web services for J2EE, Version 1.0, 6.2.2.2).
Explanation: Tried to illegally manipulate xml.
User Response: Correct your handler.

WSWS3397E: Error: JSR-109 requires that Service.getHandlerRegistry() throw an UnsupportedOperationException in a managed container.
Explanation: Cannot call this method in a managed container.
User Response: Correct your handler.

WSWS3398E: Error: JSR-109 requires that Service.getTypeMappingRegistry() throw an UnsupportedOperationException in a managed container.
Explanation: Cannot call this method in a managed container.
User Response: Correct your handler.

WSWS3399E: Error: {0} ''{1}'' didn't implement ''{2}''.
Explanation: Deployment error.
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/.

WSWS3400I: Info: unexpected exception.
Explanation: Probably an internal problem.
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/.

WSWS3401E: Error: RequestMessage missing on MessageContext.
Explanation: Internal Error.
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/.

WSWS3402E: Error: INTERNAL: ResponseMessage missing on MessageContext.
Explanation: Internal Error.
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/.

WSWS3403E: Error: Unexpected Life Cycle State: current="{0}", expected="{1}".
Explanation: Internal Error.
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/.

WSWS3404E: Error: Unexpected: SubSet({0}, {1}, {2}): acting as empty set.
Explanation: Internal Error.
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/.

WSWS3405I: Info: Ignoring exception thrown by {0}.
Explanation: Informational Message.
User Response: No action required.

WSWS3406E: Unexpected exception caught while sending reply message: {0}
Explanation: 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/.

WSWS3407E: Invalid protocol for JMS URL string: {0}
Explanation: The protocol for a JMS URL string should be "jms:"
User Response: Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.

WSWS3408E: A valid URL string can not be formed from the properties contained in the JMSURLParser object. Linked exception: {0}
Explanation: The set of properties currently contained within the JMSURLParser object cannot form a valid JMS-style URL string.
User Response: Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.

WSWS3409E: Internal Error: Client/Server mode not set for soap port.
Explanation: 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/.

WSWS3410E: Invalid value specified for the {0} property.
Explanation: The value supplied for the specified property was not correct.
User Response: Make sure that you use the correct value for the specified property.

WSWS3411E: Request timeout exceeded.
Explanation: A request did not complete within the specified timeout period.
User Response: Make sure that your server is active and is able to process requests within the allotted time.

WSWS3412E: A JMS reply message was received which did not correlate with the JMS request message.
Explanation: The JMS correlation id in the reply message did not match the JMS message id in the request message.
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/.

WSWS3413E: The JMS reply message was not of the correct JMS message type.
Explanation: The JMS reply message should be of type javax.jms.BytesMessage, but it was a different type.
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/.

WSWS3414E: Style DOCUMENT, Use LITERAL, and Wrapped do not allow operation {0} to be overloaded.
Explanation: To allow overloaded operations would cause duplicate xsi types of the same name.
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/.

WSWS3415E: Buffer size <= 0
Explanation: Internal Error.
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/.

WSWS3416E: Stream closed.
Explanation: Internal Error.
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/.

WSWS3417W: Response set in MessageContext for a one-way message. Reponse will be ignored.
Explanation: Runtime set a response message onto the MessageContext for a one-way message.
User Response: Correct JAXRPC Handler logic.

WSWS3418E: Error: Exception generated during handler fault processing.
Explanation: An exception was thrown during handler fault processing.
User Response: Inspect your handlers.

WSWS3419E: The current node is not a Text node, and it either has more than one child node or has a child node that is not a Text node.
Explanation: It's not allowed to set a value the node as described in the exception.
User Response: =CMSG0002

WSWS3420E: Error: Emitter failure. Part {0} of operation {1} must be a type part.
Explanation: The binding use is inconsistent with the parts. When the use is literal, parts can be element parts or type parts. When the use is encoded, parts must be type parts.
User Response: Fix your wsdl.

WSWS3421E: Error: The service interface ''{0}'' does not subclass ''javax.xml.rpc.Service''.
Explanation: The specified interface must subclass ''javax.xml.rpc.Service''.
User Response: Specify an interface that subclasses ''javax.xml.rpc.Service''.

WSWS3422E: Error: Can not instantiate {0}.
Explanation: The object can not be instantiated. An exception may have been logged.
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/.

WSWS3423E: Error: "javax.xml.soap.write-xml-declaration" property has to be either true or false.
Explanation: This property maps to a boolean value
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/.

WSWS3424E: Error: List value of type {1}, is not a simple type.
Explanation: xsd:list itemTypes must be atomic values.
User Response: Correct the WSDL.

WSWS3425I: From target realm: {0}.
Explanation: informational message.
User Response: no action required.

WSWS3426I: HTTP Basic Authentication information has been received.
Explanation: informational message.
User Response: no action required.

WSWS3427I: No HTTP Basic Authentication Information has been received.
Explanation: Runtime does not receive any HTTP Basic Authentication information from the prompt. Or the loginSource property is not configured.
User Response: Make sure userid and password are both entered at the prompt. Or read the InfoCenter to configure the loginSource property.

WSWS3428W: Warning: Found an old J2EE 1.3 version of the DD. A new J2EE 1.4 version will be written.
Explanation: This is notification that a previous versioned DD file was found where the DD is to be written. And that a new version will be written.
User Response: If this is unexpected, check your DD versions.

WSWS3429W: Warning: Found old J2EE 1.3 {0} file. This indicates a version mismatch - a new J2EE 1.4 DD will be written.
Explanation: This is notification that a previous versioned DD file was found where the DD is to be written. And that a new version will be written.
User Response: If this is unexpected, check your DD versions.

WSWS3430E: Invalid CharacterEncoding: {0}.
Explanation: Expected valid CharacterEncoding for incoming message.
User Response: Correct CharacterEncoding for incoming message.

WSWS3431E: Error: No Service Endpoint Class found for port {0}.
Explanation: Internal Error.
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/.

WSWS3432E: Error: Exception thrown while invoking method ''{0}'' against object ''{2}'' of class ''{3}''.
Explanation: Examine exception stack trace for more detail.
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/.

WSWS3433E: Internal Error: No Processor assigned to port {0}.
Explanation: 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/.

WSWS3434E: Unable to load configuration file
Explanation: 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/.

WSWS3435E: Error: Invalid date/time. Received an empty string for a date/time value.
Explanation: An invalid empty string date/time value was found in a soap message.
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/.

WSWS3436E: Error: Invalid time: Received an empty string for a time value.
Explanation: An invalid empty string time value was found in a soap message.
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/.

WSWS3437E: Error: Invalid date: Received an empty string for a date value.
Explanation: An invalid empty string date value was found in a soap message.
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/.

WSWS3438E: Error: The service locator ''{1}'' does not subclass the service interface ''{0}''.
Explanation: The specified service locator must subclass the service interface.
User Response: Specify a service locator that subclasses the service interface.

WSWS3439E: Error: The contents of the SOAP body are encrypted. The target operation cannot be invoked. The body contains an element with the name: {0}.
Explanation: The contents of the SOAP body should have been decrypted by web services security.
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/.

WSWS3440W: Warning: The WSDL2Java emitter does not understand qname {0} specified in field {1} of construct {2} in the mapping file: {3}. The information in the mapping file corresponding to this qname will be ignored.
Explanation: The mapping file is used to describe the java mappings for xml qnames. In this case, the qname is incorrect or not found. The corresponding information in the mapping file is ignored.
User Response: If this mapping file was created by non-IBM tooling, please contact contact the vendor. CMSG0002

WSWS3442E: Error: No output for Call.{0}.
Explanation: Call.getOutputParams and Call.getOutputValues cannot be called unless there is output. There is no output until a call to invoke returns. On a call to invokeOneWay, there is never output.
User Response: Call Call.invoke before calling Call.getOutputParams or Call.getOutputValues.

WSWS3443E: Handler {0}: Protected state violation: SOAPPart missing/removed.
Explanation: Improper use of JAX-RPC API in handler.
User Response: Review and correct use of JAX-RPC APIs.

WSWS3444E: Handler {0}: Protected state violation: SOAPMessage missing/removed.
Explanation: Improper use of JAX-RPC API in handler.
User Response: Review and correct use of JAX-RPC APIs.

WSWS3445E: Handler {0}: Protected state violation: Unexpected exception. Review error log for details.
Explanation: Improper use of JAX-RPC API in handler.
User Response: Review and correct use of JAX-RPC APIs.

WSWS3446E: The endpoint address URL is missing.
Explanation: A Web services request was made which involves the JMS transport, but the request does not include a valid endpoint address URL.
User Response: Make sure that the request contains a valid endpoint address URL. If this request was invoked within the Web Services Gateway, make sure the proper configuration has been done.

WSWS3447E: Error: Could not get a secure socket factory with the SSL settings of JSSE.
Explanation: Could not get a secure socket factory using the SSL settings of JSSE
User Response: Verify your JSSE SSL setting if you intend to use JSSE SSL setting for the SSL configuration.

WSWS3448I: Info: HTTP Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
Explanation: Configured HTTP proxy information.
User Response: None.

WSWS3449I: Info: HTTPS Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
Explanation: Configured HTTPS proxy information.
User Response: None.

WSWS3450I: Info: SSL configuration is from {0}.
Explanation: Specified SSL configuration. It can be by a java property file, a SSL configuration alias, or the JSSE SSL settings.
User Response: None.

WSWS3451I: Info: Response from Proxy for HTTP CONNECT: {0}.
Explanation: HTTP response from Proxy for the HTTP CONNECT request
User Response: None.

WSWS3452E: Internal Error: Attempted to generate code without first parsing WSDL file.
Explanation: Attempt has been made to generate the code without first parsing the WSDL file.
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/.

WSWS3453I: File {0} will NOT be written. Write permission denied by underlying file system.
Explanation: WSDL2Java issues this message if a file write attempt was denied by underlying file operating system. Most likely due to WSAD restrictions.
User Response: None.

WSWS3454E: Mixture of different settings for 'style/use' within a WSDL binding is NOT supported. Inconsistent values for the "{0}" binding are: {1}={2} and {3}={4}
Explanation: WS-I mandates that the 'style/use' must be the same for 'input/outputs' and 'faults' in any one binding. For more details visit WS-I at: http://www.ws-i.org/
User Response: Modify your WSDL document to make the 'style/use' settings for 'inputs, outputs' and/or 'faults' consistent.

WSWS3455I: Error: Invalid -javaSearch option argument "{0}". Valid options are "File", "Classpath", or "Both". Defaulting to "File".
Explanation: The -javaSearch option of WSDL2Java is wrong.
User Response: Correct the -javaSearch option setting.

WSWS3456E: Error: The onStartChild method of {0} does not know understand how to process element {1}. Processing cannot continue.
Explanation: Internal Error.
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/.

WSWS3457W: Warning: The WSDL2Java emitter has found relative namespace {0} in the WSDL, and cannot transform it to an absolute namespace.
Explanation: The wsdl has a relative namespace, such as "/home", and no ancestor absolute namespaces to pre-catenate and make an absolute namespace, such as "http://www.ibm.com/home".
User Response: Fix the namespaces in the wsdl.

WSWS3458E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible return types found at SEI method: "{0}" Existing Java return type = {1} WSDL defined return type = {2}
Explanation: Validation Error. An existing SEI class return type is not compatible with it's WSDL definition.
User Response: Correct the incompatibility between your existing SEI and WSDL document.

WSWS3459E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible parameter types found at SEI method: "{0}" Existing Java parameter type = {1} WSDL defined parameter type = {2}
Explanation: Validation Error. An existing SEI class parameter type is not compatible with it's WSDL definition.
User Response: Correct the incompatibility between your existing SEI and WSDL document.

WSWS3460E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible field types found in Java class: "{0}" Existing Java class field type = {1} WSDL defined field type = {2}
Explanation: Validation Error. An existing Java class field type is not compatible with it's WSDL definition.
User Response: Correct the incompatibility between your existing Java class and WSDL document.

WSWS3461E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Enumeration class is invalid: "{0}" Missing the following JAX-RPC required method = {1}
Explanation: Validation Error. An existing Enumeration class is missing a required method.
User Response: Add the specified method to the Enumeration class.

WSWS3462E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Enumeration class is invalid: "{0}" Contains invalid method = {1}
Explanation: Validation Error. An existing Enumeration class contains an invalid method.
User Response: Remove specified method from the Enumeration class.

WSWS3463E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" Does NOT contain a public default constructor = {1}
Explanation: Validation Error. An existing Bean class does not contain required default constructor.
User Response: Add a default constructor to specified Bean.

WSWS3464E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" It extends a non-bean class = {1}
Explanation: Validation Error. Specified Bean class does not extend an appropriate Java class.
User Response: Change the specified bean class to extend a compatible Java class.

WSWS3465E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" It does not define a bean property for the following data member = {1}
Explanation: Validation Error. Specified Bean does NOT have corresponding bean properties for it's data members.
User Response: Make the data member public, or add corresponding getters and setters.

WSWS3466E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Fault class is invalid: "{0}" It does not extend = {1}
Explanation: Validation Error. Specified fault class is not a Java Exception class.
User Response: Make the specified fault class extend java.lang.Exception.

WSWS3467E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Fault class is invalid: "{0}" Does not implement a valid public constructor: "{1}", containing {2} parameters.
Explanation: Validation Error. Specified Fault class does not implement a constructor with correct number of parameters.
User Response: Make sure Fault class implements a public constructor with required parameters.

WSWS3468E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Fault class is invalid: "{0}" It does not define a property for the following data member = {1}
Explanation: Validation Error. Specified Fault class does NOT have corresponding bean properties for it's data members.
User Response: Make the data member public, or add corresponding getters and setters.

WSWS3469E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible parameter types found at Fault class method: "{0}" Existing Java parameter type = {1} WSDL defined parameter type = {2}
Explanation: Validation Error. An existing Fault class parameter type is not compatible with it's WSDL definition.
User Response: Correct the incompatibility between your existing Fault class and WSDL document.

WSWS3470E: Error while running class ''{0}''.
Explanation: 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/.

WSWS3471W: Binding {0} has already been generated and will not be re-generated.
Explanation: None.
User Response: None.

WSWS3472W: One-way operations were requested for methods returning 'void', but operation ''{0}'' has been declared to throw a fault, so it will be converted into a two-way operation.
Explanation: None.
User Response: None.

WSWS3473E: No binding generator was found for binding type ''{0}''.
Explanation: An unsupported binding type was requested.
User Response: Ensure that only valid binding types are requested.

WSWS3474I: Found a binding generator for binding type ''{0}''.
Explanation: None.
User Response: None.

WSWS3475W: A binding specific location property was not specified for the requested {0} binding. The default location ''{1}'' will be used.
Explanation: None.
User Response: None.

WSWS3476W: The generic -location option should not be used when more than one binding type has been requested.
Explanation: You have requested more than one binding type with the -bindingTypes option, but you have specified a single endpoint location URI with the -location option. When requesting multiple binding types, you should specify binding-specific endpoint location URI values for each of the requested binding types by using the .location properties instead of using the -location command-line option.
User Response: Specify multiple endpoint location URI values with the -properties option.

WSWS3477I: Binding-specific properties are {0}
Explanation: None.
User Response: None.

WSWS3479E: The ''{0}'' property is required, but was not specified.
Explanation: Required property needs to be specified.
User Response: Specify required property.

WSWS3480E: One or more errors occurred while validating the input properties.
Explanation: See previously reported errors.
User Response: Fix cause of previously reported errors.

WSWS3481E: There is no binding defined for {0} RequestSender.
Explanation: 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/.

WSWS3482E: There is no deployment descriptor defined for {0} RequestSender.
Explanation: 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/.

WSWS3483E: Could not find WSDL file ''{0}'' within the EAR.
Explanation: WSLD file could not be found where it was expected.
User Response: Fix the EAR.

WSWS3484E: Caught {0} while trying to read WSDL file ''{1}'': {2}
Explanation: 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/.

WSWS3485E: No WSDL services were found for namespace ''{0}''.
Explanation: 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/.

WSWS3486E: The ClassLoader parameter was passed in as null.
Explanation: The ClassLoader parameter is required for the method to function properly, but a null value was passed in.
User Response: Ensure that a non-null value is passed in for the ClassLoader parameter.

WSWS3487E: The port name and service ref name are both null.
Explanation: 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/.

WSWS3488E: Error: This SOAPElement is not a swaRef - it is not a reference to an attachment.
Explanation: Either this SOAPElement does not contain a text node, or the text node does not refer to an attachment.
User Response: Make sure this is a swaRef element by calling isSwaRef.

WSWS3489E: Error: Mime type {0} does not match object type {1}.
Explanation: The mimeType must be consistent with the object: image/gif, image/jpeg ==> java.awt.Image text/plain ==> java.lang.String multipart/* ==> javax.mail.internet.MimeMultipart text/xml, application/xml ==> javax.xml.transform.Source (actually, javax.xml.transform.stream.StreamSource) all others ==> javax.activation.DataHandler
User Response: Make sure the parameters to addSwaRefTextNode are consistent.

WSWS3490E: Error: The system cannot load the file referenced within {0}. The problem is with {1}.
Explanation: File specified by user was not found in the file system.
User Response: Make sure file exists and/or that it was spelled correctly.

WSWS3491E: Error: Reading import file: {0}
Explanation: Import ile specified by in wsdl was not found in the file system.
User Response: Make sure file exists and/or that it was spelled correctly.

WSWS3492W: Warning: Invalid option combination: style={0} and use={1} Will default to document/literal.
Explanation: document/encoded is an invalid combination of style/use.
User Response: Use a valid combination of style/use: rpc/encoded rpc/literal document/literal

WSWS3493E: Error: Invalid combination: style="{0}" and use="{1}" For binding="{2}" and binding operation="{3}"
Explanation: document/encoded is an invalid combination of style/use.
User Response: Use a valid combination of style/use: rpc/encoded rpc/literal document/literal

WSWS3494I: syncTimeout value is {0} seconds to wait for response to the current SOAP over {1} request.
Explanation: Configured syncTimeout value in seconds.
User Response: None.

WSWS3495I: {0} is used as the final endpoint address.
Explanation: None.
User Response: None.

WSWS3496I: {0} is used as the proxy address.
Explanation: None.
User Response: None.

WSWS3497I: Status in the HTTP response: {0}, {1}
Explanation: Inform the HTTP response from the server.
User Response: None.

WSWS3498E: No HTTP status has been received for the current HTTP response.
Explanation: No HTTP status information is available to determine the HTTP response.
User Response: Make sure the target HTTP server is up.

WSWS3499W: Redirected new location: {0}
Explanation: Received HTTP response indicates a new location for the target resource.
User Response: User may want to check WebSphere InfoCenter for details about how to accept the automatic redirection to the new location.

WSWS3500I: Required service: {0} from JNDI namespace: {1}
Explanation: None.
User Response: None.

WSWS3501E: Failures from the Channel Framework service: {0}
Explanation: There are failures from the Channel Framework service.
User Response: Check errors reported by Channel Framework service in the log.

WSWS3502E: Unsupported schema for HTTP: {0}
Explanation: Found unsupported schema for using HTTP transport.
User Response: Verify the target endpoint address.

WSWS3503I: Updated configuration of the outbound connection for key: {0}
Explanation: None.
User Response: None.

WSWS3504E: Failed to retrieve HTTP(S) proxy information for the proxy connection.
Explanation: Runtime failed to get the HTTP proxy information to process the proxy connection.
User Response: Make sure the HTTP or HTTPS proxy information is configured properly. User may want to check WebSphere InfoCenter about how to configure for HTTP proxy.

WSWS3505I: Creating channel named: {0}
Explanation: None.
User Response: None.

WSWS3506I: Found channel named: {0}
Explanation: None.
User Response: None.

WSWS3507I: Creating channel chain named: {0}
Explanation: None.
User Response: None.

WSWS3508I: Found channel chain named: {0}
Explanation: None.
User Response: None.

WSWS3509I: Expect 100 Continue in the HTTP response...sending HTTP request headers only to connection: {0}
Explanation: The Expect 100-Continue header is set. Only HTTP request headers are sent to determine if server is willing to accept the HTTP request.
User Response: None.

WSWS3510I: Sending both HTTP request headers and body message to connection: {0}
Explanation: None.
User Response: None.

WSWS3511I: Sending current request to {0} in version: {1}
Explanation: Sending current SOAP over HTTP request in indicated HTTP version.
User Response: None.

WSWS3512E: Unsupported HTTP version: {0}
Explanation: Unsupported HTTP version is detected. This is an internal error.
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/.

WSWS3513E: Invalid HTTP response received from the connection for: {0}
Explanation: Invalid HTTP response is received. This could be an internal error.
User Response: None.

WSWS3514E: No HTTP response body is available from the connection for: {0}
Explanation: There are failures with the HTTP Channel service.
User Response: Check errors reported by HTTP Channel service in the log.

WSWS3515E: Failures with the SSL Channel services: {0}
Explanation: There are failures with the SSL Channel service.
User Response: Check errors reported by SSL Channel service in the log.

WSWS3516I: Received cookie for HTTP header: {0} in the response from connection to: {1}
Explanation: None.
User Response: None.

WSWS3517I: Target address to connect: {0}
Explanation: None.
User Response: None.

WSWS3518I: Target address: {0} is already connected.
Explanation: None.
User Response: None.

WSWS3519I: Disconnecting target address: {0}. Mark the object to be closed: {1}
Explanation: None.
User Response: None.

WSWS3520I: Target address: {0} is already disconnected. The connection object: {1} is already marked.
Explanation: None.
User Response: None.

WSWS3521I: Reset the connection object for target address: {0}. Connection is persistent? {1}
Explanation: None.
User Response: None.

WSWS3522I: Read keystore password property for: {0}
Explanation: Indicate how many keystore password properties have been identified.
User Response: None.

WSWS3523E: The serialization engine detected an element nesting greater than 100 elements. This exceeds the limit of the serialization engine. This problem was found while serializing an object of class: {0}
Explanation: An attempt was made to serialize a message with too deep a nesting. This could be due to a linked list with too many nodes. This problem could also be due to an attempt to serialize a graph containing looped references.
User Response: Please correct the data being serialized.

WSWS3524E: The requested WSDL document is not displayed because there are no SOAP ports present in the requested WSDL. Use the /extwsdl query to access the full WSDL document.
Explanation: Appending "/wsdl" to a service URL is a request to retrieve a WSDL document that contains SOAP ports for the HTTP or JMS transports. If there are no such ports, this error is displayed instead of the WSDL document.
User Response: Modify the query to obtain the extended wsdl or contact the Web service owner.

WSWS3525E: Exception occurred while loading "META-INF/services/CustomBindingProvider.xml" files.
Explanation: The engine or tool failed to parse the CustomBindingProvider.xml to build the CustomProvider object.
User Response: Check the CustomBindingProvider.xml files to see whether there are any syntax error.

WSWS3526W: No namespace was found for a mapping defined in the file {0}.
Explanation: It's expected that every custom type mapping has a non-default namespace.
User Response: Correct the CustomBindingProvider.xml file.

WSWS3527I: Discovered and loaded the custom binding provider from the file: {0}
Explanation: None
User Response: None

WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ---------- Extension base mismatch between existing Bean and WSDL document. Existing Bean class: "{0}" Extends the following class: {1} However the following extension base is specified in the WSDL document: {2}
Explanation: Validation Error. Specified Bean class does not extend same extension base specified in WSDL document.
User Response: Change the specified Bean class or WSDL document to extend appropriate Java class.

WSWS3529I: Outbound connection object expired: {0}. Time from the last access to the object: {1} millieseconds.
Explanation: None.
User Response: None.

WSWS3530I: Found an existed outbound connection object: {0} in the cache.
Explanation: None.
User Response: None.

WSWS3531I: Created a new outbound connection object: {0} in the cache using virtual connection factory: {1}
Explanation: None.
User Response: None.

WSWS3532I: Returning a closed outbound connection object: {0} to the cache.
Explanation: None.
User Response: None.

WSWS3533I: Returning an outbound connection object: {0} to the cache.
Explanation: None.
User Response: None.

WSWS3534W: Encountered unknown outbound connection object: {0}
Explanation: Runtime found an unknown outbound connection object. It could be an internal error.
User Response: Check for connection exception in the log.

WSWS3535I: Remove outbound connection object: {0} from the cache.
Explanation: None.
User Response: None.

WSWS3536I: New connection established with virtual connection object: {0}
Explanation: None.
User Response: None.

WSWS3537I: Connection established already with virtual connection object: {0}
Explanation: None.
User Response: None.

WSWS3538W: A connection is attempted with outbound connection object that is already marked to be closed: {0}
Explanation: Access to a closed connection is attempted. This could be an internal error.
User Response: Check for connection exception in the log.

WSWS3539E: Exception {0} is caught. Release related virtual connection object:{1} and outbound service context: {2}
Explanation: An exception has caused the release of saved virtual connection object and outbound service context.
User Response: Check from the log for the previous exception caught.

WSWS3540I: Key {0} found for connection table lookup: {1}
Explanation: None.
User Response: None.

WSWS3541E: Error: Attribute {0} is referenced but not defined.
Explanation: WSDL2Java error indicating that an attribute is referenced but no definition was found.
User Response: Please correct your wsdl.

WSWS3542I: Each failed HTTP connection will be retried until succeeds.
Explanation: Based on a Java system property setting, each HTTP connection will be retried until the connection succeeds. However, this is not recommended as deadlock may happen.
User Response: User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections.

WSWS3543I: Number of retries for failed HTTP connection: {0}.
Explanation: Based on a Java system property setting, each HTTP connection will be retried for the configured number of times. However, user needs to be cautious about changing this property as deadlock may sometimes happen. Default value is 3.
User Response: User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections.

WSWS3544W: Exception caught: {0}. HTTP connection to retry: {1}.
Explanation: The reported exception is caught, but the HTTP connection will be retried until the configured number of times is reached.
User Response: User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections.

WSWS3545I: Released object: {0}
Explanation: None.
User Response: None.

WSWS3546I: Current size of the connection object pool: {0}
Explanation: None.
User Response: None.

WSWS3547I: Outbound connection group is created for key: {0}
Explanation: None.
User Response: None.

WSWS3548W: Warning: WSDL2Java could not discover a suitable StubWriter. The default SOAP StubWriter will be used.
Explanation: Internal discovery problem, perhaps with classloader.
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/.

WSWS3549E: Error: WSDL2Java could not discover a suitable StubWriter for {0}.
Explanation: Internal discovery problem, perhaps with classloader. Can't continue.
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/.

WSWS3550E: Error: The MessageContext specifies Style {0} but the OperationDesc specifies Style {1}.
Explanation: A bad property detected on the MessageContext or OperationDesc. This could be caused by an internal error.
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/.

WSWS3551E: Error: The MessageContext specifies Use {0} but the OperationDesc specifies Use {1}.
Explanation: A bad property detected on the MessageContext or OperationDesc. This could be caused by an internal error.
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/.

WSWS3552E: Error: Can not load the Java class for the custom binder: {0}.
Explanation: Either the above custom binder does not exist or it is not in the classpath for the context classloader.
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/.

WSWS3553E: Error: The value of -MIMEstyle must be AXIS, swaRef or WSDL11.
Explanation: The -MIMEstyle option of Java2WSDL is incorrect.
User Response: Use a correct -MIMEstyle option.

WSWS3554E: Error: Group {0} is referenced but not defined.
Explanation: WSDL2Java error indicating that a group is referenced but no definition was found.
User Response: Please correct your wsdl.

WSWS3555E: Error: AttributeGroup {0} is referenced but not defined.
Explanation: WSDL2Java error indicating that a attributeGroup is referenced but no definition was found.
User Response: Please correct your wsdl.

WSWS3556I: No compression will be performed for HTTP Content-Encoding.
Explanation: There will be no compression performed for the HTTP content encoding in the HTTP request or the HTTP response. Hence, the Web services property for HTTP compression has been ignored.
User Response: User can consider the followings: 1.) validate the value of Web services property for HTTP compression, 2.) check for error messages from HTTP Channel, or 3.) do nothing if compression is not needed.

WSWS3557I: Compression type of enabled? {0}
Explanation: Indicate whether the described compression type are enabled. Note that gzip and x-gzip use the same compression mechanism.
User Response: Check the Web services property for HTTP compression is configured as needed.

WSWS3558I: Compression type of enabled? {0}
Explanation: Indicate whether the compression type of deflate is enabled.
User Response: Check the Web services property for HTTP compression is configured as needed.

WSWS3559I: Using {0} type of HTTP Channel.
Explanation: Indicate what type of HTTP Channel is used for HTTP connection. It could be an In-process or network type.
User Response: None.

WSWS3560W: Unable to get an Inprocess Channel: {0}. Proceed now with a network type of Channel.
Explanation: There might be an error when the system attempted to find an Inprocess HTTP Channel. However, this may not be a problem unless an in-process connection is required. The system will proceed with a network type of Channel instead.
User Response: If necessary, check the trace for Work Load Management(WLM) or Dynamic Work Load Management Client(DWLMclient) errors.

WSWS3561E: Mapped to cluster name <{0}> using - host: {1}, port: {2}, URI path: {3}
Explanation: The printed data was used to map to a valid cluster name.
User Response: None.

WSWS3562W: Warning: The -wrapped option setting is only useful if -style DOCUMENT and -use LITERAL. Processing continues and the wrapped setting is ignored.
Explanation: The -wrapped option is only applicable if -use LITERAL and -style DOCUMENT.
User Response: Remove the -wrapped option or set the -use/-style options correctly.

WSWS3563I: Accept-Encoding header from incoming HTTP request = {0}
Explanation: This indicates the value set by the web services client for acceptable content-codings in the HTTP response. Please refer to the specification of Hypertext Transfer Protocol for further details. Header value of null indicates empty Accept-Encoding header in the incoming HTTP request;hence, no content encoding is done in the HTTP response.
User Response: If it is a WebSphere Web services client, check the Web services property for Http compression encoding of the target service port. Make sure the value is configured properly.

WSWS3564I: ChannelFramework EndPoint object: {0} is mapped, using Identity object of {1}
Explanation: This printed data was used to map for a channelframework endpoint object that can be used later to create In-process connection.
User Response: None.

WSWS3565E: Error: Invalid endpoint argument to Service.getPort {0}
Explanation: The specified endpoint was used to invoke Service.getPort.
User Response: Correct the invocation of Service.getPort.

WSWS3566E: Error: Invalid port for Service.createCall: {0}
Explanation: The specified port was used to invoke Service.createCall.
User Response: Correct the invocation of Service.createCall.

WSWS3567E: Error: Invalid operation for Service.createCall: {0}
Explanation: The specified operation was used to invoke Service.createCall.
User Response: Correct the invocation of Service.createCall.

WSWS3568E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" It does not define a set method for the following data member = {1} A get method was found = {2}
Explanation: Validation Error. Specified Bean does not correctly define a bean property for the designated data member.
User Response: Make the data member public, or add an appropriate setter method. Be particularly careful to ensure that the get and set methods use the same capitalization.

WSWS3569I: Inbound {0} {1} request: Content-Type: {2} Message contents:
Explanation: The following message was received as a Web services request.
User Response: None.

WSWS3570I: Inbound {0} {1} response: Content-Type: {2} Message contents:
Explanation: The following message was received in response to a previous Web services request.
User Response: None.

WSWS3571I: Outbound {0} {1} request: Content-Type: {2} Message contents:
Explanation: The following message was sent as a Web services request.
User Response: None.

WSWS3572I: Outbound {0} {1} response: Content-Type: {2} Message contents:
Explanation: The following message was sent as a response to a Web services request.
User Response: None.

WSWS3573E: Cluster identity object: {0} found by the RequestMapper using original endpoint address: {1}. If the identity object is null, transport will proceed to use default channels for connections.
Explanation: The RequestMapper of Dynamic Work Load Management Client may have or have not found a matching cluster identity. If the object is null, transport will proceed to use default channels for connections.
User Response: If Clustering is used, check for errors from Dynamic Work Load Management Client(DWLMClient) in trace.

WSWS3574E: ---------- FATAL ERRORS ENCOUNTERED ---------- GENERATION OF ARTIFACTS HAS BEEN SUSPENDED. See messages to follow for more details.
Explanation: Fatal errors have been encountered most likely due to user error. More details in messages to follow. Code/Artifacts generation has been suspended.
User Response: Correct problems reported and try again.

WSWS3575E: Failed to set the protection for the SOAPBody.
Explanation: Attempted to protect the SOAP message body befor invoking the JAX-RPC handlers, however, an unknown error occurred while doing so.
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/.

WSWS3576I: Info: Changed java name {0} to {1} for xml construct {2} due to mapping file reference.
Explanation: The JSR109 mapping file defined a name for the xml construct that is different than the default mapping.
User Response: none

WSWS3577I: Info: Changed java name {0} to {1} for xml construct {2} due to custom binding designation.
Explanation: The custom binder defined a name for the xml construct that is different than the default mapping.
User Response: none

WSWS3578I: Info: Changed java name {0} to {1} for xml construct {2} due to java reflection.
Explanation: Java reflection indicates that the name of the xml construct that is different than the default mapping.
User Response: none

WSWS3579I: Info: Introspecting SEI {0}. JavaClass is: {1}
Explanation: Performing introspection of indicated SEI.
User Response: none

WSWS3580I: Info: Introspecting class for xml construct {0}. JavaClass is: {1}
Explanation: Performing introspection of indicated class.
User Response: none

WSWS3581E: Error: PortType operation has no corresponding binding operation: name = {0}, input name = {1}, output name = {2}
Explanation: An invalid portType operation was encountered in the wsdl.
User Response: Please correct the wsdl.

WSWS3582E: The ''{0}'' property is invalid unless -bindingTypes http (or no bindingTypes) is also specified.
Explanation: When property is specified, the corresponding property must also be specified.
User Response: Respecify the property using bindningTypes http.

WSWS3583E: The ''{0}'' property is invalid unless -bindingTypes jms is also specified.
Explanation: When property is specified, the corresponding property must also be specified.
User Response: Respecify the property using bindningTypes jms.

WSWS3584E: The ''{0}'' property is invalid unless -bindingTypes ejb is also specified.
Explanation: When propertie is specified, the corresponding property must also be specified.
User Response: Respecify the property using bindingTypes ejb.

WSWS3585W: Warning: PortType operation has no corresponding binding operation containing the same number of input and output parameter names. name = {0}, input name = {1}, output name = {2}
Explanation: Inconsistent portType and binding operation were encountered in the wsdl.
User Response: Make sure wsdl is correct.

WSWS3586I: Invoking method: {0}() of class: {1}
Explanation: none.
User Response: none

WSWS3587I: Received Cluster Identity object: {0} from WS-Addressing. If the Identity object is null, transport attempts to map one by the RequestMapper.
Explanation: The indicated Identity object has been received from WS-Addressing. If null, transport will attempt to map one by the RequestMapper.
User Response: If clustering is used, check for errors from WS-Addressing in the trace.

WSWS3588I: Could not map an Cluster Identity object: {0} to a valid endpoint. Transport attempts to use default channels for connections.
Explanation: The indicated Identity object cannot be mapped to a valid endpoint.
User Response: If null, check for errors from Clustering and ChannelFramework in the trace.

WSWS3589I: Exception caught: {0} resolving the endpoint. Proceed to next option using RequestMapper.
Explanation: An exception was caught. However, the exception can be benign since transport can proceed to next option using the RequestMapper to resolve the endpoint.
User Response: If applicable, check for errors related to WS-Addressing.

WSWS3590I: Exception caught: {0} resolving the endpoint. Proceed to next option using default channels.
Explanation: An exception was caught. However, the exception can be benign since transport can proceed to next option using the default channels to resolve the endpoint.
User Response: If applicable, check for errors related to Dynamic Work Load Management Client.

WSWS3591I: An exception which was defined in the WSDL for the the operation has been thrown by the service endpoint. This may not indicate an error.
Explanation: The service endpoint implementation has thrown an exception. This may or may not indicate an error in the service endpoint implementation.
User Response: Contact the owner of the service endpoint implementation to determine if this exception indicates normal processing or an error condition.

WSWS3592E: Error: Could not resolve to an operation. The message contains body elements named ""{0}"", and this matches multiple operations ""{1}"". Debug: {2}
Explanation: This may be a symptom of an incorrect wsdl.
User Response: Fix your wsdl to remove ambiguity, or CMSG002

WSWS3593E: Error: Operations {0} and {1} have the same parameters elements in their input request message. Please change the wsdl.
Explanation: Document/Literal operations must have unique parameter elements in their input message so that the target server can determine which operation is invoked.
User Response: Fix your wsdl to remove ambiguity.

WSWS3594E: Error: Methods {0} and {1} have the same parameters names. A document literal non-wrapped wsdl cannot be produced.
Explanation: Document/Literal operations must have unique parameter elements in their input message so that the target service can determine which operation is invoked.
User Response: Specify the -wrapped true option

WSWS3595I: Current pool size: {0}. Connections-in-use size: {1}. Configured pool size: {2}
Explanation: This informational message describes the current condition of the outbound HTTP connection pool.
User Response: No user action is required.

WSWS3596I: Current thread: {0} is going to wait for notification.
Explanation: Indicates that the connection pool is full and that the current thread is waiting for openings. The run time might wait for a very long time if the network is busy.
User Response: If the wait is too long, consider specifying a connection wait timeout, or increase the number of maximum connections, or both. Check for network problems.

WSWS3597I: Current thread: {0} is going to wait {1} milliseconds for notification.
Explanation: Indicates that the connection pool is full and that the current thread is waiting for openings for the specified amount of time. If no opening is available, a "Connection timed out" exception might result.
User Response: If the exception is found,consider increasing the maximum connections value for the connection pool, and the connection wait timeout value to wait for openings in the pool. Check for network problems.

WSWS3598I: Notify the next waiting thread.
Explanation: None.
User Response: No user action is required.

WSWS3599I: The current thread: {0} has been notified.
Explanation: None.
User Response: No user action is required.

WSWS3600I: The connection wait timed out.
Explanation: This message is seen with a WebServicesFault exception. The connection wait for an opening in the connection pool has been reached and no connection object is available.
User Response: Consider increasing the connection wait timeout, and increasing the maximum connections value.Check for network problems.

WSWS3601E: An unexpected integrity problem occurred with the connection pool.
Explanation: 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/.

WSWS3602I: Current endpoint: {0}. New endpoint: {1}
Explanation: None.
User Response: No user action is required.

WSWS3700E: Error: Non-whitespace character content ({0}) was detected in the {1}. Processing cannot continue.
Explanation: The indicated construct cannot have mixed character content.
User Response: Correct the SOAP message.

WSWS3701E: Error: An exception was encountered. Use the wsdeploy command to deploy your application. The exception is {0} {1}
Explanation: An unexpected exception occurred, and the run time has detected generated code from a different build.
User Response: Deploy your application again with the wsdeploy command. CMSG0002

WSWS3702E: Error: Could not resolve to an operation. The message contains an element named ""{0}"", but this element does not match any operation of the target port. However, the following operation(s) ({1}) have similar information but are a different style. This difference might indicate that the client sent a {2} message and the server is expecting a {3} message. Debug: {4}
Explanation: It is possible that the client and the server have different operation styles. This symptom can indicate a Web service deployment problem or an incorrect SOAP request message.
User Response: Correct the client message so that it matches the style that is expected on the server.

WSWS3703E: Error: The WSDL operation, {2}, contains multiple {1} parameters that are mapped to the same qname: {0}.
Explanation: The parameters in the SOAP message must be unique.
User Response: Change the WSDL message part name and the element attributes to ensure unique parameters.

WSWS3704W: Warning: Java2WSDL encountered a inner nested class named {0} in the input. Inner classes are not supported. Generation will continue.
Explanation: The input SEI references a class nested inside another class. This is unsupported.
User Response: Change the Java structure.

WSWS4001E: The SOAP address should have the form http|https://host:port. An improperly formatted SOAP address was supplied for Module {0}. The incorrect SOAP address is {1}.
Explanation: The user input is incorrect for the SOAP address.
User Response: Provide the correct SOAP address.

WSWS4002E: The router module for module {0} could not be found.
Explanation: The application has not been properly enabled for Web services. A Web services-enabled EJB module does not have the required router WAR module.
User Response: Properly enable the application for Web services.

WSWS4003E: The router module for EJB module {0} is {1}. The router module's web.xml file is missing a URL pattern for port component {2}
Explanation: The router module is not configured correctly.
User Response: Configure the router module correctly.

WSWS4004E: The wsdl-file {1} for module {0} was not found in the module.
Explanation: The module is not configured correctly.
User Response: Configure the module correctly.

WSWS4005E: An exception occurred while adding URL prefixes to the published WSDL file. The exception is {0}
Explanation: The explanation is provided by the exception.
User Response: Respond to the action provided by the exception.

WSWS4006E: WSWS406E the JMS URL prefix {0} is not correctly formatted. The JMS URL prefix must start with jms:/[queue|topic]?, and the destination and connectionFactory must not contain java:comp
Explanation: The user input for the JMS URL prefix is incorrect.
User Response: Provide the JMS URL prefix in the correct format.

WSWS4007E: Can not retrieve application metadata for application{1}, exception:{0}
Explanation: This indicates a programming error has occurred.
User Response: Report the error.

WSWS4008E: Error: {0}
Explanation: Error.
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/.

WSWS4009E: The Web service binding file, {1}, does not contain a {0} element.
Explanation: The binding file does not contain expected elements.
User Response: Fix the bindings file.

WSWS4010E: An error occurred initializing the WSDL zip files. Check the log for more information.
Explanation: An error can occur when creating and writing temporary WSDL zip files.
User Response: Check the log for more information.

WSWS4011E: An error occurred preparing or initializing one or more of the follwing WSDL zip file names: {0}
Explanation: An error can occur when creating and writing temporary WSDL zip files.
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/.

WSWS4012E: The WSDL zip file contains no ports. Check the log for more information.
Explanation: The WSDL file does not contain port information.
User Response: Check the log for more information.

WSWS4050E: Transform error occurred: {0}
Explanation: An error occurred while attempting to perform XSL transform on the deployment descriptor.
User Response: Check the nested exception for details.

WSWS4051E: This application might not contain the Web services deployment descriptor information you need.
Explanation: The workspace returned a null pointer for the input stream to the deployment descriptor.
User Response: Check the application installation.

WSWS4052E: No input stream obtained for the deployment descriptor.
Explanation: The workspace returned a null pointer for the input stream to the deployment descriptor.
User Response: Check the application installation.

WSWS4053E: Could not load deployment descriptor through the user workspace. Exception: {0}
Explanation: The deployment descriptor could not be accessed for processing.
User Response: Check the nested exception for details.

WSWS4054E: Unable to transform. No resource type specified to transform.
Explanation: The view request did not specify what type of resource this was. For example, an application descriptor or EJB descriptor.
User Response: Check the installation of this resource to insure it is properly installed.

WSWS4055E: No output stream obtained for the deployment descriptor.
Explanation: Transformer returns a null pointer for the output stream to the deployment descriptor.
User Response: Check the application installation.

WSWS4056E: A SAX parser exception occurred.
Explanation: Transformer catches a SAX parser exception.
User Response: Check the application installation.

WSWS4057E: A SAX parser configuration exception occurred.
Explanation: Transformer catches a SAX parser configuration exception.
User Response: Check the application installation.

WSWS5001E: {0} is null.
Explanation: A null value was passed for the specified parameter, and this is not valid for this particular operation.
User Response: Make sure that a non-null value is passed in for the specified parameter.

WSWS5002E: Input parameter {0} was passed in as null, but {1} has not been called.
Explanation: If a null argument is going to be passed in, then the specified method should be called to set the type of each argument.
User Response: Make sure that you first call the appropriate method to set the argument types, or make sure that you do not pass a null argument to the 'invoke' method.

WSWS5003E: Caught {0} while retrieving method ''{1}'' from class ''{2}'': {3}
Explanation: The specified exception was caught while attempting to retrieve the specified method from the specified class.
User Response: Make sure that the specified EJB class contains the appropriate methods.

WSWS5004E: Caught {0} while invoking method ''{1}'' on class ''{2}'': {3}
Explanation: The specified exception was caught while attempting to invoke the specified method from the specified class.
User Response: Make sure that the specified EJB class contains the appropriate methods.

WSWS5005E: {0} is not an interface.
Explanation: The specified parameter should be an interface, not a class.
User Response: Make sure that the parameter is passed in as an interface.

WSWS5006E: Class {0} is not an instance of EJBHome or EJBLocalHome.
Explanation: The specified class name should refer to a valid EJBHome class, but the class is not an instance of EJBHome or EJBLocalHome.
User Response: A class name which refers to a valid EJBHome or EJBLocalHome class should be passed in.

WSWS5007E: Caught {0} while attempting to locate the following JNDI name: {1} {2}
Explanation: An error was encountered while attempting to do a JNDI lookup of the specified JNDI name.
User Response: Make sure that the correct JNDI lookup name is specified within the endpoint location URI.

WSWS5008E: Caught {0} while trying to obtain an InitialContext object.
Explanation: The specified exception was caught while trying to create an InitialContext object which would be used to perform JNDI lookup operations.
User Response: Use the exception details to determine how to resolve the problem.

WSWS5009E: Caught {0} while attempting to create protocol-specific Call object: {1}
Explanation: 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/.

WSWS5010E: Error: Cannot find port: {0}
Explanation: The specified port could not be found by Service.getPort.
User Response: Correct the invocation of Service.getPort.

WSWS5011E: Method {0} is not supported in a managed environment.
Explanation: Within the managed J2EE environment, the Service.getTypeMappingRegistry and Service.getHandlerRegistry methods are not supported. They may only be called within the unmanaged JSR-101 client environment.
User Response: Make sure that you do not call these methods when the client application is running within the J2EE managed environment.

WSWS5012E: Error loading generated Stub class ''{0}'': {1}
Explanation: The specified exception was thrown while a generated Stub class was being loaded.
User Response: Make sure that the specified Stub class exists and is available to be loaded.

WSWS5013E: No constructor with the signature {0} was found for generated Stub class ''{1}'': {2}
Explanation: The specified generated Stub class should have a constructor with the specified signature.
User Response: Make sure that the proper Stub class is being used.

WSWS5014E: Error instantiating generated Stub class ''{0}'': {1}
Explanation: The specified exception was thrown when a new instance of the generated Stub class was being created.
User Response: Make sure that the proper generated Stub class is being used.

WSWS5015E: No WSDL definition was found at URI: {0}
Explanation: The ServiceFactory.createService method was unable to find a WSDL definition at the specified location.
User Response: Make sure that the WSDL document is available and that the WSDL location is correct.

WSWS5016E: The WSDL definition located at URI ''{0}'' did not contain Service ''{1}''.
Explanation: The specified WSDL definition was located, but it did not contain the specified Service.
User Response: Make sure that the WSDL document contains the correct Service and that you are using the correct Service name.

WSWS5017E: Error reading WSDL definition located at URI: {0}
Explanation: The specified WSDL document was either not found, or contained an error.
User Response: Make sure that the WSDL document exists and that it is correct.

WSWS5018E: Caught {0} while trying to invoke method ''{1}'' from class ''{2}'': {3}
Explanation: An exception was thrown while attempting to invoke a method from the specified class.
User Response: Make sure that the specified EJB class contains the appropriate methods.

WSWS5019E: Error obtaining Service for port ''{0}'': {1}
Explanation: 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/.

WSWS5020E: Error obtaining Stub class ''{0}'': {1}
Explanation: The specified exception was thrown while an attempt was made to obtain an instance of the generated Stub class.
User Response: Make sure that the generated Stub class is available to be loaded.

WSWS5021E: Error obtaining port ''{0}'': {1}
Explanation: An error occurred while trying to obtain the Stub for the specified port.
User Response: Make sure that the generated Stub object exists and that the port name is correct.

WSWS5022E: Error while trying to create extension for parent type ''{0}'' and element type ''{1}''.
Explanation: 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/.

WSWS5023E: Invalid protocol in endpoint location URI: {0}
Explanation: The specified endpoint location URI contains an incorrect protocol.
User Response: Correct the endpoint location URI.

WSWS5024E: Missing '=' in query string within endpoint location URI: {0}
Explanation: An error was found while parsing the specified endpoint location URI.
User Response: Correct the endpoint location URI.

WSWS5025E: Invalid attribute name: {0}
Explanation: The caller tried to set or get the value for the specified attribute from an ExtensibilityElement, but the attribute name is not a valid name.
User Response: Make sure that a valid attribute is used.

WSWS5026E: Internal error: duplicate shadow registry.
Explanation: 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/.

WSWS5027E: Invalid property name for Call object: ''{0}''
Explanation: An attempt was made to set or get the specified property on a Call object, but the property name is not valid.
User Response: Make sure that you are using a valid property name.

WSWS5028E: Caught {0} while trying to close a transport: {1}
Explanation: 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/.

WSWS5029E: Caught {0} while processing a method invocation: {1}
Explanation: An exception was thrown during the processing of a method request.
User Response: Use the detailed information from the error message to determine the cause of the error.

WSWS5030E: Invalid method: {0}
Explanation: 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/.

WSWS5031E: Invalid Service Endpoint Interface: ''{0}''. No WSDL definition available.
Explanation: When calling Service.getPort(Class), the WSDL definition is required but was not available.
User Response: Make sure the WSDL definition is available.

WSWS5032E: Invalid Service Endpoint Interface: ''{0}''. No default port available.
Explanation: When calling Service.getPort(Class), a default port is required but was not available.
User Response: Make sure that a default port exists for the Service Endpoint Interface.

WSWS5033E: Cannot create a dynamic proxy without a WSDL definition.
Explanation: If a generated Stub class is not found, then a dynamic proxy will be created, but the WSDL definition is required.
User Response: Make sure the WSDL definition is available.

WSWS5034E: Cannot create a dynamic proxy without a port QName.
Explanation: If a generated Stub class is not found, then a dynamic proxy will be created, but a non-null port name is required.
User Response: Make sure that a non-null port name is passed in.

WSWS5035E: Port ''{0}'' does not exist.
Explanation: The specified port is not a valid port for the service.
User Response: Correct the port name.

WSWS5036E: No WSDL definition is available.
Explanation: The Service.getPorts() method cannot return the list of ports unless the WSDL definition is available.
User Response: Make sure the WSDL definition is available.

WSWS5037E: The {0} is not supported by the {1} class.
Explanation: 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/.

WSWS5038I: not used
Explanation: None.
User Response: None.

WSWS5039I: not used
Explanation: None.
User Response: None.

WSWS5040I: not used
Explanation: None.
User Response: None.

WSWS5041E: Error getting protocol from endpoint location URI: ''{0}''
Explanation: An error occurred while trying to obtain the protocol of the specified endpoint location URI.
User Response: Make sure the endpoint location URI is correct.

WSWS5042E: Invalid protocol found in WSDL endpoint location URI. Expected {0}, but found {1}.
Explanation: An unexpected protocol value was found in the endpoint location URI.
User Response: None.

WSWS5043E: The Service class ''{0}'' does not implement the ''{1}'' interface.
Explanation: A JAX-RPC Service class must implement the specified interface in order to conform to the JAX-RPC specification. In this situation, the Web services runtime loaded a class assumed to be a valid Service class, but it does not implement the expected interface.
User Response: Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool.

WSWS5044E: The required constructor was not found for the generated Service class: ''{0}''
Explanation: See error message.
User Response: Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool.

WSWS5045E: {0}: empty port name found in WSDL port names array.
Explanation: 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/.

WSWS5046E: Caught {0} getting EJB class name from endpoint location URI ''{1}'': {2}
Explanation: The EJB class name could not be obtained from the specified endpoint location URI.
User Response: Correct the endpoint location URI.

WSWS5047E: Caught {0} getting properties from endpoint location URI ''{1}'': {2}
Explanation: An error occurred while parsing the properties contained in the specified endpoint location URI.
User Response: Correct the endpoint location URI.

WSWS5048E: The {0} property is missing from endpoint location URI ''{1}''.
Explanation: A required property was missing from the endpoint location URI.
User Response: Correct the endpoint location URI.

WSWS5049E: Caught an unexpected exception while trying to instantiate a target object of class ''{0}'': {1}
Explanation: Unable create an instance of the specified implementation class.
User Response: Refer to the exception in the original error message to determine how to resolve the problem.

WSWS5050E: Caught {0} while trying to initialize target object of class ''{1}'': {2}
Explanation: Unable to initialize an instance of the specified implementation class.
User Response: Refer to the exception in the original error message to determine how to resolve the problem.

WSWS5051E: Caught {0} while trying to load target object class ''{1}'': {2}
Explanation: Unable to load the specified implementation class.
User Response: Make sure that the implementation class is available to be loaded.

WSWS5052E: Caught {0} getting implementation class name from endpoint location URI ''{1}'': {2}
Explanation: Unable to obtain the implementation class name from the endpoint location URI.
User Response: Correct the endpoint location URI.

WSWS5053E: Caught {0} while trying to get method ''{1}'' on target class ''{2}'': {3}
Explanation: Unable to find the specified method on the specified implementation class.
User Response: Make sure that the correct implementation class is being used.

WSWS5054E: Caught {0} while trying to invoke method ''{1}'' on target class ''{2}'': {3}
Explanation: An exception was thrown while invoking the specified method.
User Response: Refer to the exception in the original error message to determine how to resolve the problem.

WSWS5055E: Could not find a Service for namespace ''{0}''.
Explanation: 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/.

WSWS5056E: Cannot create a dynamic proxy due to exception: {0}
Explanation: A JAXRPC dynamic proxy Stub could not be created for the specified port and service endpoint interface.
User Response: Check that the specified service endpoint interface is valid.

WSWS5057E: There is no PortType in the WSDL defintion for the specified service endpoint interface: ''{0}''.
Explanation: The service endpoint interface name passed to the getPort method must match a PortType in the WSDL for this Service.
User Response: Make sure that the service endpoint interface matches a PortType defined in the WSDL.

WSWS5058E: Invalid Service Endpoint Interface: ''{0}'' is not an interface.
Explanation: When calling Service.getPort(Class), the service endpoint interface must specify an Interface.
User Response: Make sure that the Service Endpoint Interface specifies an interface, not a class.

WSWS6000E: Error: {0}
Explanation: 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/.

WSWS6001E: Recieved request {0} for unregistered system service endpoint {1}.
Explanation: Request received for a system application that has not been installed and deployed.
User Response: Verify the system endpoint name and check for errors during server startup.

WSWS6002E: No system endpoint router defined for request {0}.
Explanation: There is no router defined for the incoming request.
User Response: Verify that there are valid system services endpoints with valid system endpoint configuration files.

WSWS6003I: SOAP Container Service has been initialized.
Explanation: The SOAP Container Service has not been initialized.
User Response: None. This is an information-only message.