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