Explanation | These are the options to WSDL2Java. |
Action | Use the specified options when invoking WSDL2Java. |
Explanation | These are the extended options to WSDL2Java. |
Action | These are advanced options that users should not generally use. |
Explanation | These are the options to Java2WSDL. |
Action | Use the specified options when invoking Java2WSDL. |
Explanation | These are the extended options to Java2WSDL. |
Action | These are advanced options that users should not generally use. |
Explanation | The -location option is a required option. |
Action | Specify the -location option. Example: -location http://thisServer:9080 |
Explanation | The -server-side option is incorrect. |
Action | Specify the correct -server-side option. |
Explanation | The -transport option is incorrect. |
Action | Specify the correct option. Example -transport jms |
Explanation | This pre-existing operation has an output element. It is removed. |
Action | No user action is required. |
Explanation | This pre-existing operation has a fault element. It is removed. |
Action | No user action is required. Operations without an output must be considered one-way and faultless. |
Explanation | The emitter is loading the specified class. |
Action | No user action is required. |
Explanation | The emitter is generating the indicated construct. |
Action | No user action is required. |
Explanation | A Java Message Service (JMS) endpoint URL must specify either queue or topic as the destination type. |
Action | Correct the JMS endpoint URL and retry. |
Explanation | A Java Message Service (JMS) endpoint URL string contains an unrecognized property. |
Action | Correct the JMS endpoint URL and retry. |
Explanation | A Java Message Service (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. |
Action | Correct the JMS endpoint URL and retry. |
Explanation | The Application Server cannot create a Java Naming and Directory Interface (JNDI) InitialContext object. |
Action | Use the detailed information in the original error message to determine the problem. |
Explanation | The specified error occurred during a Java Naming and Directory Interface (JNDI) lookup operation. |
Action | Ensure that the JNDI name is correct. |
Explanation | A Java Message Service (JMS) operation resulted in the specified JMSException. |
Action | Use the detailed information in the original error message to determine how to correct the problem. |
Explanation | An Exception was caught in Java Message Service (JMS) processing. |
Action | Use the detailed information in the Exception to determine how to correct the problem. |
Explanation | The specified exception occurred when a request was being processed. |
Action | Use the detailed information in the original error message to determine how to correct the problem. |
Explanation | The specified WebServicesFault exception occurred during Java Message Service (JMS) processing. |
Action | Use the detailed information in the original error message to determine how to correct the problem. |
Explanation | The message-driven bean listener for Web services cannot retrieve a configured server engine during its initialization. |
Action | 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/ . |
Explanation | The JMSSender did not set the indicated property on the Java Message Service (JMS) request message prior to sending the message to the destination queue or topic. This error is an internal error. |
Action | Ensure that the JMS sender uses the required property. |
Explanation | The Web services Java Message Service (JMS) listener received a JMS message that was not a TextMessage or a BytesMessage type. The JMS listener supports only these two JMS message types. |
Action | Ensure that the JMS sender uses the correct JMS message type. |
Explanation | A two-way request/response was invoked for a topic destination, but only one-way requests are supported when you use a topic. |
Action | Ensure that any services which use topic destinations contain only one-way operations. Ensure that, within the Web Services Description Language (WSDL) file, the operation does not contain an output message. |
Explanation | An internal error has occurred during processing of an attachment. A multi part attachment must have a root part. |
Action | 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/ . |
Explanation | This error occurs when an incorrect mapping file is provided to the WSDL2Java tool. |
Action | Correct your mapping file. |
Explanation | The -voidReturn option is incorrect as it must be accompanied by the oneway or twoway value. |
Action | Specify the correct option. |
Explanation | The message is not a legal SOAP message. |
Action | Contact the originator of the message. |
Explanation | The _Helper class is needed for proper serialization or deserialization. Serialization or deserialization might fail. |
Action | Ensure that the _Helper class is properly emitted by WSDL2Java tool and the class deployed correctly. |
Explanation | Some xml constructs cannot be mapped to Java types. |
Action | The application code needs to use the SOAPElement methods to construct and analyze the data. |
Explanation | An internal error occurred. This error is possibly due to an error in the deployment information. |
Action | 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/ . |
Explanation | The indicated object cannot be serialized. |
Action | Make sure that a proper serializer is registered. |
Explanation | The Application Server used either a keystore and truststore pair or a cryptographic token to get a secure socket factory. |
Action | No user action is required. |
Explanation | The indicated type cannot be deserialized. |
Action | Make sure that a proper deserializer is registered. |
Explanation | This internal error occurs because the start up code is incorrect. |
Action | 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/ . |
Explanation | The handler generated an unexpected RuntimeException exception. The JAX-RPC Version 1.0 (JSR-101) specification requires that a SOAPFaultException exception be generated by the server. See the output or error log for the original exception. |
Action | Correct the handler code to eliminate the RuntimeException exception. |
Explanation | The handler generated an unexpected RuntimeException exception. The JAX-RPC Version 1.0 (JSR-101) specification requires that a SOAPFaultException exception be generated by the server. See the output or error log for the original response message. |
Action | Correct the handler code to eliminate the RuntimeException exception. |
Explanation | The Application Server cannot serialize the indicated object. |
Action | Make sure that the correct serializer is registered. |
Explanation | The Application Server cannot deserialize the indicated object. |
Action | Make sure that the correct deserializer is registered. |
Explanation | The Application Server cannot access a deleted memory-managed data source. |
Action | 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/ . |
Explanation | The arrayType attribute in the SOAP message is not valid. |
Action | 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/ . |
Explanation | Basic authentication only is supported with the SimpleServerEngine. The SimpleServerEngine is only for debugging. It is not for production use. |
Action | Do not use the SimpleServerEngine for production uses. |
Explanation | A Boolean value in the SOAP message must be 0, 1, true, or false. |
Action | Correct the SOAP Boolean. |
Explanation | A calendar value in the SOAP message is not valid. |
Action | Correct the SOAP calendar. |
Explanation | A character in a hex string in the SOAP message is not valid. |
Action | Correct the SOAP hex string. |
Explanation | A bad date value exists in the SOAP message. |
Action | Correct the SOAP date. |
Explanation | A bad date or time value exists in a SOAP message. |
Action | Correct the SOAP date or time. |
Explanation | The specified bean does not have a property that matches the element. The soap message cannot be deserialized. If the WSDL's schema contains elementFormDefault="qualified", the element should be qualified with a prefix, or should exist in a default namespace. If the schema contains elementFormDefault="unqualified" or completely omits this attribute, the element should not be qualified, and does not have a namespace at all. |
Action | 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/ . |
Explanation | An attempt was made to deploy the indicated class as a Handler class. However the class does not extend the Handler class. |
Action | Correct your deployment information. |
Explanation | An attempt was made to use the specified class as a Holder. However the class does not extend the Holder interface. |
Action | Correct your Holder class. |
Explanation | The SOAP message contains an array that has a non-integer array length. The Application Server cannot deserialize the SOAP message. |
Action | Correct the SOAP message array. |
Explanation | This error normally occurs as a result of an internal error in the deployment software. |
Action | 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/ . |
Explanation | The envelope element of the SOAP message has an incorrect namespace. The Application Server cannot deserialize the message. |
Action | Correct the SOAP message namespace. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | The offset attribute for the indicated array in the SOAP message is not valid. The Application Server cannot deserialize the SOAP message. |
Action | Correct the SOAP message. |
Explanation | An internal exception occurred with the WSDL2Java emitter. |
Action | 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/ . |
Explanation | The position attribute for the indicated array in the SOAP message is not valid. The Application Server cannot deserialize the SOAP message. |
Action | Correct the SOAP message. |
Explanation | The portName argument to the service.getCalls method must be a recognized port name. |
Action | Ensure that the argument to the service.getCalls method is appropriate. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | SimpleServerEngine does not understand the request. The SimpleServerEngine is only for debugging. It is not for production use. |
Action | Do not use the SimpleServerEngine for production uses. |
Explanation | The argument for the scope option must be Request, Application, or Session. |
Action | Use the proper -scope option when invoking the WSDL2Java tool. |
Explanation | The SOAP message does not contain an envelope element. |
Action | Correct the SOAP message. |
Explanation | A bad time value was found in the SOAP message. |
Action | Correct the SOAP message. |
Explanation | A bad timezone was found in the SOAP message. |
Action | Correct the SOAP message. |
Explanation | A problem has occurred in the deployment software. |
Action | 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/ . |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | Normally, this error is caused by a SOAP message that is not valid. |
Action | Correct the SOAP message. |
Explanation | This error might occur as a result of a SOAP message that is not valid. |
Action | 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/ . |
Explanation | The Application Server cannot authenticate the user. |
Action | Specify a correct authenticated known user. |
Explanation | The Application Server cannot authenticate the user. |
Action | Specify a correct authenticated user. |
Explanation | User is not authorized. |
Action | Specify a correct authorized user. |
Explanation | This error is an internal error. The Web services engine cannot convert the SOAP message into bytes. |
Action | Fix the cause of the inconsistent SOAP message. |
Explanation | This error is an internal error. The Web services engine cannot convert the SOAP message into a String. |
Action | Fix the cause of the inconsistent SOAP message. |
Explanation | The indicated value cannot be assigned to the bean field. The Web services engine cannot deserialize the SOAP message. |
Action | Fix the cause of the inconsistent SOAP message. |
Explanation | This error is an internal error. The Web services engine cannot convert a value into an int. |
Action | Fix the cause of the inconsistent types. |
Explanation | This error is an internal error. The Web services engine cannot serialize a null array. |
Action | Fix the cause of the null array. |
Explanation | This error occurs because there is a problem with the tool options. For more information, see the other associated messages. |
Action | Fix the URL. |
Explanation | This message normally indicates that the SOAP message is not valid. The Web services engine was expecting a simple value when it encountered a child element. The Web services engine cannot deserialize the SOAP message.. |
Action | Fix the cause of the not valid SOAP message. |
Explanation | An internal error has occurred. The QName of the request target has a null namespace. |
Action | 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/ . |
Explanation | The Web services engine cannot serialize the indicated class with the array serializer. |
Action | Suspect a problem with the deployment information. |
Explanation | The element serializer can only be used to serialize org.w3c.dom.Element objects. |
Action | 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/ . |
Explanation | The SimpleSerializer cannot be used to serialize a non-registered object. |
Action | Make sure your this class is registered with an appropriate type. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Webservices Engine cannot make the appropriate tunnel. |
Action | 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/ . |
Explanation | Attempting to change the password using the AdminClient interface is not supported. |
Action | AdminClient is not fully supported. |
Explanation | The SOAP with Attachments API for Java (SAAJ) model is being used incorrectly. |
Action | 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/ . |
Explanation | This error message occurs as a result of an internal error. |
Action | Do not use the AdminClient interface, it is not fully supported. |
Explanation | This error message occurs as a result of an internal error within WSDD deployment. |
Action | 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/ . |
Explanation | The connection is closed. The Web services engine cannot make the remote service call. |
Action | 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/ . |
Explanation | WSDL2Java issues this message if different QNames result in the creation of the same Java file. |
Action | Fix the Web Services Description Language (WSDL) document or use the NStoPkg options to differentiate the classes. |
Explanation | The parameter order attribute in the WSDL is incorrect. |
Action | Fix the Web Services Description Language (WSDL) document. |
Explanation | The emitter cannot locate the endpoint address. |
Action | Fix the Web Services Description Language (WSDL) document. |
Explanation | The endpoint address is not valid. |
Action | Change the Web Services Description Language (WSDL) file so that valid endpoint address is associated with the port. |
Explanation | Specify a binding for the service Web Services Description Language (WSDL) port. |
Action | Fix the Web Services Description Language (WSDL) file. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The binding must be defined in the Web Services Description Language (WSDL) document if it is referenced there. |
Action | Fix the Web Services Description Language (WSDL) File. |
Explanation | The binding must be defined in the Web Services Description Language (WSDL) document if it is referenced there. |
Action | Fix the Web Services Description Language (WSDL) File. |
Explanation | The portType must be defined in the Web Services Description Language (WSDL) document if it is referenced there. |
Action | Fix the Web Services Description Language (WSDL) File. |
Explanation | The portType must be defined in the Web Services Description Language (WSDL) document if it is referenced there. |
Action | Fix the Web Services Description Language (WSDL) File. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | Problem occurred when the Web services engine attempted to invoke a remote Web service. |
Action | 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/ . |
Explanation | An administrative error occurred when translating XML into deployment operations. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | This error is likely the result of a SOAP message that is not valid. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web services engine cannot read the specified directory. |
Action | Fix your configuration, check permission flags. |
Explanation | The serialization process that is being used might cause performance issues. |
Action | Examine code and make appropriate changes. |
Explanation | The -container option for the WSDL2Java emitter is incorrect. |
Action | Fix the -container option by using ejb, web, client, or none as the value. |
Explanation | The -role option for the WSDL2Java emitter is incorrect. |
Action | Fix the -role option by using develop-client, deploy-client, develop-server, or deploy-server as the value. |
Explanation | The Web service always runs in a Web or Enterprise JavaBeans (EJB) container. |
Action | Fix the options and rerun the WSDL2Java emitter. |
Explanation | This error is most likely due to a previous error with the Web services deployment descriptor. |
Action | Review the log for previous errors. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Web services engine cannot find the specified service. |
Action | Verify the name of the service that is specified by the client. Also, verify the deployment of that service on the server. |
Explanation | The was-webservices.xml configuration file defines a handler Java class that does not implement the expected interface. |
Action | Specify the Java class that implements the expected interface. |
Explanation | The -genJava option for the WSDL2Java emitter is incorrect. |
Action | Correct the -genJava option so that uses No, IfNotExists, or Overwrite for its value. |
Explanation | The -genXML option for the WSDL2Java emitter is incorrect. |
Action | Correct the -genXML option so that uses No, IfNotExists, or Overwrite for its value. |
Explanation | The Web services engine cannot obtain a secure socket factory. |
Action | Correct the Secure Sockets Layer (SSL) configuration. |
Explanation | Error occurred during deployment. This is probably an internal error. |
Action | 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/ . |
Explanation | This message might result to a deserialization error, but there are multiple reasons for this message. Look for other errors. |
Action | 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/ . |
Explanation | The getPort method requires a proxy interface. |
Action | Correct the invocation of the getPort method. |
Explanation | The proxy class argument must be an interface that extends the java.rmi.Remote interface. |
Action | Fix the invocation of the getPort method. |
Explanation | You must specify a password for the AdminClient interface. |
Action | Specify a password. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | No user was found to authorize. |
Action | 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/ . |
Explanation | You cannot administer remotely. |
Action | The Admin class is not fully supported. |
Explanation | A body was expected in the SOAP envelope, but the Web services engine cannot find this message part. Thus cannot deserialize the SOAP message. |
Action | 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/ . |
Explanation | The Web services engine cannot deserialize the array of the indicated component type. |
Action | This problem might be due to deployment information that is not valid. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The SOAP message is not valid and the Web services engine cannot deserialize the message. |
Action | 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/ . |
Explanation | Normally this message occurs as a result of bad client or server deployment information. |
Action | 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/ . |
Explanation | Nornally this message occurs as a result of a bad SOAP message or server deployment information that is not valid. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error probably occurred. |
Action | 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/ . |
Explanation | The configuration data is not valid. |
Action | 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/ . |
Explanation | Internal Error with deployment information. |
Action | 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/ . |
Explanation | Missing information in deployment information. |
Action | 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/ . |
Explanation | Missing handlers in deployment information. |
Action | 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/ . |
Explanation | The header information is missing from the SOAP message. |
Action | 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/ . |
Explanation | The SOAP message is not valid. The Web services engine cannot deserialize the message due to the processing instructions. |
Action | 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/ . |
Explanation | The MapSerializer cannot serialize the object. This message is probably the result of an internal deployment error. |
Action | 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/ . |
Explanation | The deployment information is not complete. This message is probably the result of an internal error. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web Services Description Language (WSDL) file does not define any operations in the portType. This error is an internal error or a deployment error. |
Action | Check the logs for deployment problems. |
Explanation | The Web Services Description Language (WDSL) binding does not specify the operation. |
Action | Fix the Web Services Description Language (WSDL) File. |
Explanation | The indicated option was not found for the service. |
Action | 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/ . |
Explanation | The parameter order attribute must reference a message part. |
Action | Fix the Web Services Description Language (WSDL) File. |
Explanation | The specified port could not be found by Service.getPort. |
Action | Correct the invocation of Service.getPort. |
Explanation | The deployed Web Services Description Language (WSDL) is missing the portType. |
Action | Fix the deployed Web Services Description Language (WSDL) File. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | This message indicates that an internal error occurred with the deployment information. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web services engine received a request for the specified target service, but the engine configuration did not contain a port with this name. |
Action | Compare the endpoint location URL that is being used by the client application with the endpoint location URL contained in the corresponding WSDL document. If you are using the HTTP protocol, make sure that the client application is using the correct URL pattern within the endpoint location URL. If you are using the JMS protocol, make sure that your client application is using an endpoint location URL that contains the correct targetService property. Within a JMS-style endpoint location URL, the targetService property should be set to the name of the desired port component. |
Explanation | A security provider is necessary for this MessageContext. |
Action | Make sure a security provider is configured. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web services engine cannot serialize the indicated array component type. |
Action | Make sure the indicated array component type is registered. |
Explanation | The Web services engine cannot deserialize the component of the vector. |
Action | 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/ . |
Explanation | The type attribute is missing from the deployment information. |
Action | 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/ . |
Explanation | The QName is missing from the deployment information in the type mapping registry. |
Action | 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/ . |
Explanation | An authorized user is required. |
Action | 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/ . |
Explanation | The Handler did not understand mustUnderstand headers. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | Processing cannot continue because the indicated item is null. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | AdminClient is not fully supported. |
Explanation | The Namespace argument must be specified. |
Action | 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/ . |
Explanation | The Web services engine attempted to call the SOAP with Attachments API for Java (SAAJ) setParent method with a null argument. This error might be the result of an internal error. |
Action | 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/ . |
Explanation | Missing deployment information. This may be the result of an internal error. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web services engine cannot construct the HexBinary object. |
Action | Determine the cause of the odd number of digits and correct. |
Explanation | The SOAP message contains multiple SOAP body parts inside the envelope. The Web services engine cannot deserialize the SOAP message. |
Action | Determine the origin of the SOAP message and correct the cause. |
Explanation | The SOAP message contains multiple SOAP headers inside the envelope. The Web services engine cannot deserialize the SOAP message. |
Action | Determine the origin of the SOAP message and correct the cause. |
Explanation | The number of parameters does not match the expected number of parameters. This could be a DII or internal error. |
Action | 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/ . |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A problem occurred when the Web services engine attempted to deserialize the SOAP message. |
Action | 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/ . |
Explanation | The AdminClient interface encountered an error processing the indicated file. The AdminClient is not fully supported. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Administration service is quitting. The Administration class is not fully supported. |
Action | No action is required. |
Explanation | An internal error has occurred. The SimpleServerEngine is not fully supported. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is set into a WebServicesFault. |
Action | No action is required. |
Explanation | The WEB-INF directory might not be accessible. |
Action | Correct problem with the WEB-INF directory. |
Explanation | The configuration file for the servlet engine might not be accessible. |
Action | Correct problem with the configuration file for the servlet engine. |
Explanation | This is a warning message. The process will be attempted again differently. |
Action | No user action required. |
Explanation | A configuration error occurred during the attempt to load the configuration file from the Java archive (JAR) file. |
Action | 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/ . |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Web Services Description Language (WSDL) part must specify the type or element attribute. |
Action | Correct the deployed WSDL file by adding the type or element attribute. |
Explanation | Internal Error or problem with input SOAP message. |
Action | 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/ . |
Explanation | The Admin tool encountered an unknown host. The Admin tool is not fully supported. |
Action | Determine origin of the unknown host problem and correct it. |
Explanation | An error has occurred with the Admin tool. The Admin tool is not fully supported. |
Action | 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/ . |
Explanation | Normally, this message represents an error with the deployed Web Services Description Language (WDSL) file that has been detected during service creation. |
Action | Correct the deployed WSDL. |
Explanation | A Web Services Description Language (WSDL) document is needed to use the Service.getPort method. |
Action | Correct the deployment information. |
Explanation | An internal error occured in the WSDL2Java SymbolTable. |
Action | 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/ . |
Explanation | The Web Services Description Language (WSDL) file references types or elements that are not defined. |
Action | Correct the WSDL file. |
Explanation | There is likely a problem with your Java Naming and Directory Interface (JNDI) configuration. |
Action | Correct your JNDI configuration. |
Explanation | An InitialContext was not created. |
Action | Inspect other errors to determine why InitialContext was not created. |
Explanation | The Web services engine found a recursive definition of the indicated type or element. |
Action | Correct your Web Services Description Language (WSDL) file. |
Explanation | The Web services engine detected a bad property on the call or the MessageContext. This message might be caused by an internal error. |
Action | Fix the property. |
Explanation | The Web services engine detected a bad property. This message might be caused by an internal error. |
Action | Determine origin of null property name if possible, and correct. |
Explanation | A null property value was specified. This message might be caused by an internal error. |
Action | Determine origin of null property value if possible, and correct. |
Explanation | The specified property is not supported. |
Action | Discontinue use of the specified property. |
Explanation | Normally, this error message is due to an internal error that is associated with the serialization engine. |
Action | 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/ . |
Explanation | Normally, this error message is due to an internal error that is associated with the deserialization engine. |
Action | 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/ . |
Explanation | Normally, this error message is due to an internal error with the serialization engine. |
Action | 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/ . |
Explanation | The isRegistered method requires a non-null Java class. This error might be the result of an internal problem. |
Action | 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/ . |
Explanation | The isRegistered method requires a non-null qualified name (QName). This error might be the result of an internal problem. |
Action | 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/ . |
Explanation | Normally, this error suggests that a problem occurred with the deployment software. |
Action | Check the deployment logs for related problems. |
Explanation | The Web Services Description Language (WSDL) file contains unsupported MIME constructs. |
Action | Correct the WSDL, |
Explanation | The Web Services Description Language (WSDL) service name is wrong. |
Action | Correct the WSDL service name. |
Explanation | The bean attributes must be simple types. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | The attributes must be simple types. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | A problem ocurred when the Web services engine created the JAX-RPC Handler. |
Action | Review the reasons for why the Web services engine creates this exception. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Normally, this error message indicates a problem with the deployed type mapping registry. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | This error message is used in conjuction with other exceptions. |
Action | See the associated exception messages. |
Explanation | This error message is used in conjuction with other exceptions. |
Action | See the associated exception messages. |
Explanation | Normally, this error message indicates that an internal error has occurred. |
Action | 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/ . |
Explanation | An error has occurred when the Web services engine attempted to configure the parser. |
Action | Correct the parser configuration. |
Explanation | Indicates that a SAX Exception has occurred. Normally the exception is due to a problem configuring the parser. |
Action | Correct the parser configuration. |
Explanation | Normally, this error message indicates that an internal error has occurred. |
Action | 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/ . |
Explanation | Normally, this error message indicates a problem with a MIME message. |
Action | 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/ . |
Explanation | Normally, this error message indicates an internal error. |
Action | 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/ . |
Explanation | Normally, this error message indicates an internal error. |
Action | 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/ . |
Explanation | Normally, this error message indicates an internal error. |
Action | 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/ . |
Explanation | This error message originates from overloaded message processing of a SOAPPart, AttachmentPart. or SOAPHeader. |
Action | 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/ . |
Explanation | This error message originates from overloaded method processing of a SOAPElement. |
Action | 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/ . |
Explanation | A problem occurred when the Web service engine attempted to invoke the indicated target. |
Action | 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/ . |
Explanation | This error may indicate a problem with MIME attachments. |
Action | 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/ . |
Explanation | Malformed URL Exception occurred in the SimpleServerEngine. |
Action | 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/ . |
Explanation | A WebServicesFault exception has occurred. |
Action | For more information, see the associated messages. |
Explanation | This message is for informational purposes only. |
Action | No action is required. See other messages for details about why the fault was issued. |
Explanation | This message is for informational purposes only. |
Action | No action is required. See other messages for details about why the fault was issued. |
Explanation | The Web Services Description Language (WSDL) file or one of it's imported documents is not accessible. |
Action | Make sure the WSDL and any imported documents are accessible. You can also increase the timeout & retry values through the WSDL2Java emitter options. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An operation has been invoked on a Stub or Call object, However, a target endpoint address was not set. |
Action | Ensure that the target endpoint address has been set on the Stub or Call object prior to invoking the operation. |
Explanation | The Web services engine encountered an unsupported attachment type. |
Action | Use a supported attachment type. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web services engine attempted to access a closed stream. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | Data Handler has no content. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | Make sure that your engine configuration is correct. |
Explanation | The Web services engine did not expect Child elements in the SOAP message. Thus, the SOAP message cannot be deserialized. |
Action | 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/ . |
Explanation | The Web Services Description Language (WSDL) file is missing the correct type resolution. |
Action | Correct the WSDL. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The type mapping cannot change after registration has occurred. |
Action | Correct your application and re-try. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The registration of the TypeMapping is not valid. |
Action | Correct your application and re-try. |
Explanation | The default type mapping cannot change after registration. |
Action | Correct your application and re-try. |
Explanation | You cannot call the getPort method because a stub implementation of the interface does not exist. |
Action | Correct your application and re-try. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | This may be a symptom of a Web service deployment problem or an incorrect SOAP request message. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | JavaBeans must have default constructors. |
Action | Make sure that the JavaBean has a default constructor. |
Explanation | A bad argument has been specified for -soapAction option. |
Action | Use the correct -soapAction option for the Java2WSDL emitter. |
Explanation | A problem has ocurred with the Web service deployment, with the SOAP message, or hot swapping of the SoapBindingImpl class for the service. |
Action | 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/ . |
Explanation | This message, which is for informational purposes only, indicates which Java classes are generated by the WSDL2Java emitter. |
Action | No action is required. |
Explanation | The -style option of Java2WSDL emitter is incorrect. |
Action | Use either the DOCUMENT or RPC value for the -style option. |
Explanation | A Web service deployment error might have ocurred, and is being detected in the ServiceFactory. |
Action | 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/ . |
Explanation | A Web service deployment error might have ocurred, and is being detected in the JavaBeanDispatcher. |
Action | 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/ . |
Explanation | Yon can specify one class file only for the Java2WSDL emitter. |
Action | Correct the invocation of the Java2WSDL emitter. |
Explanation | You must specify a class file for the Java2WSDL emitter. |
Action | Correct the invocation of the Java2WSDL emitter. |
Explanation | You can only specify the Web Services Description Language (WSDL) file once for the WSDL2Java emitter. |
Action | Correct the invocation of the WSDL2Java emitter. |
Explanation | You must specify the Web Services Description Language (WSDL) URI for the WSDL2Java emitter. |
Action | Correct the invocation of the WSDL2Java emitter. |
Explanation | The value is incorrect for the enumeration. |
Action | Correct your application and re-try. |
Explanation | This Java2WSDL error indicates that the class cannot be converted into an XML schema type. All Java class files have mappings to XML schema types. Converting an existing Java service into a Web service using the Java2WSDL emitter is not guaranteed. |
Action | All of the Java classes that are part of your Web service interface must have the appropriate mappings to the Web Services Description Language (WSDL) file. This action is necessary so that a client to the service can automatically generate the interface and all of the related classes to access your Web service. |
Explanation | This Java2WSDL error indicates that the class cannot be converted into an XML schema type. All Java class files have mappings to XML schema types. Converting an existing Java service into a Web service using the Java2WSDL emitter is not guaranteed. |
Action | All of the Java classes that are part of your Web service interface must have the appropriate mappings to the Web Services Description Language (WSDL) file. This action is necessary so that a client to the service can automatically generate the interface and all of the related classes to access your Web service. |
Explanation | This Java2WSDL error indicates that the class cannot be converted into an XML schema type. All Java class files have mappings to XML schema types. Converting an existing Java service into a Web service using the Java2WSDL emitter is not guaranteed. |
Action | All of the Java classes that are part of your Web service interface must have the appropriate mappings to the Web Services Description Language (WSDL) file. This action is necessary so that a client to the service can automatically generate the interface and all of the related classes to access your Web service. |
Explanation | The WSDL2Java emitter does not support this XML Schema type. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | Each message part must have an element or type attribute which locates the schema element/type. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | A problem might have occurred when the Application Server deployed the Web service. |
Action | 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/ . |
Explanation | A problem might have occurred when the Application Server deployed the Web service, which likely indicates an internal error. |
Action | 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/ . |
Explanation | The NormalizedString object cannot be set because the value of the object is not valid. |
Action | Correct the normalizedString value. |
Explanation | The Token object cannot be set because the value of the object is not valid. |
Action | Correct the token value. |
Explanation | An internal error has occurred. |
Action | Make sure that the indicated class complies with the JAX-RPC technology. |
Explanation | The Web services engine cannot write the schema for the indicated class. This error message is probably due to an internal error. |
Action | 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/ . |
Explanation | The class is not valid. |
Action | Verify that you have specified a class to the Java2WSDL emitter. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | This Java2WSDL error indicates that the class cannot be converted into an XML schema type. All Java class files have mappings to XML schema types. Converting an existing Java service into a Web service using the Java2WSDL emitter is not guaranteed. |
Action | All of the Java classes that are part of your Web service interface must have the appropriate mappings to Web Services Description Language (WSDL) file. This action is necessary so that a client to the service can automatically generate the interface and all of the related classes to access your Web service. |
Explanation | An error has ocurred with the WSDL2Java emitter. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | This WSDL2Java emitter message is for informational purposes only. |
Action | No action is required. |
Explanation | An error occurred when the Web services engine attempted to construct a YearMonth object. |
Action | Use a correct value. |
Explanation | An error occurred when the Web services engine attempted to construct a Year object. |
Action | Use a correct value. |
Explanation | An error occurred when the Web services engine attempted to construct a Month object. |
Action | Use a correct value. |
Explanation | An error occurred when the Web services engine attempted to construct a Day object. |
Action | Use a correct value. |
Explanation | An error occurred when the Web services engine attempted to construct a MonthDay object. |
Action | Use a correct value. |
Explanation | An error occurred when the Web services engine attempted to construct a Duration object. |
Action | Use a correct value. |
Explanation | This speicifed serializer cannot be used to serialize attributes. |
Action | Please correct the deployed type mappings. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An attempt was made to use the SourceDataHandlerSerializer serializer to serialize a non-SourceStream object. |
Action | 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/ . |
Explanation | An internal error has occurred. This error usually indicates that information is missing in the PortDesc or WSDDPort in regards to the definition of the Web service operations. The engine attempts to deduce the missing information, which might result in this particular error. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | This message is warning of a missing method. |
Action | Correct your factory implementation. |
Explanation | The Web services engine cannot invoke the method. |
Action | Correct your factory implementation. |
Explanation | The factory implementation is missing. |
Action | Correct your factory implementation or its location. |
Explanation | The Web services engine cannot load the indicated factory. |
Action | Make sure that the factory can be loaded. |
Explanation | The deployment information for WSDD is missing. This error might be due to an internal error. |
Action | 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/ . |
Explanation | The deployment information for WSDD is missing. This error might be due to an internal error. |
Action | 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/ . |
Explanation | This WSDL2Java error indicates that an element is referenced but a definition was not found. |
Action | Correct the Web Services Description Language (WSDL) file so that the element is defined. |
Explanation | A type or ref attribute is used to reference a type or element. However, the attribute is missing. |
Action | Correct the Web Services Description Language (WSDL) file so that the attribute is specified. |
Explanation | This error message might be due to deployment problems. |
Action | Make sure that the classloaders can locate and load the indicated class. |
Explanation | Normally, this error message indicates that the deployment information is missing or incorrect. |
Action | Correct the implementation or location. |
Explanation | An internal error occurred. The specified application programming interface (API) is not supported. |
Action | Use only supported APIs. |
Explanation | An internal error occurred. This is an unsupported api. |
Action | Use only supported APIs. |
Explanation | The Web Services Description Language (WSDL) file contains a binding operation that is not valid. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The SOAP request message that has been received by the service does not match the Web Services Description Language (WSDL) definition. |
Action | Make sure that the SOAP message that was sent to the service matches the WSDL definition. |
Explanation | The binding fault must have a corresponding portType fault. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | The binding fault must have a name. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | The binding fault must have an appropriate <soap:fault> element. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | The SOAP message is incorrect. |
Action | Attempt to determine the origin of the SOAP, and correct. |
Explanation | The response SOAP message is incorrect. |
Action | Attempt to determine the origin of the SOAP, and correct. |
Explanation | The -use option for the Java2WSDL emitter is incorrect. |
Action | The -use option must use the LITERAL or ENCODED values. |
Explanation | The -extraClasses option for the Java2WSDL emitter is incorrect. |
Action | Correct the -extraClasses option. |
Explanation | A method was encountered that has a return type, but the Java2WSDL emitter has been invoked in a mode that assumes that the method is one way. |
Action | Correct the class so that method uses the correct mode. |
Explanation | This error message is likely the result of an internal error. |
Action | 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/ . |
Explanation | This error message is likely the result of an internal error. |
Action | 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/ . |
Explanation | This error message can result from an internal error or a bad input SOAP message. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The Web services engine cannot add a child SOAPElement element to the indicated object. |
Action | Correct your application code. |
Explanation | The Web services engine cannot add the indicated child element. |
Action | Correct your application code. |
Explanation | The Web services engine cannot add a Text node to the indicated object. |
Action | Correct your application code. |
Explanation | The Web services engine cannot call the setAttributes method after the SOAPElement has attributes. |
Action | Correct your application code. |
Explanation | The Web services engine cannot call the setMappingScope method after the SOAPElement has a MappingScope. |
Action | Correct your application code. |
Explanation | This error message is a result of an unrecognized alternate content type. |
Action | Correct your application code. |
Explanation | The Web services engine expected only one child element of the given qualified name (QName). |
Action | Correct your application code. |
Explanation | An attempt was made to set alternate content on a SOAPElement that already has alternate content. |
Action | Make sure you remove the existing alternate content before replacing it. |
Explanation | The indicated prefix does not have a corresponding namespace Uniform Resource Indicator (URI). |
Action | Correct your application code or SOAP message. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The SOAP message contains an illegal xmlns prefix. |
Action | 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/ . |
Explanation | The Admin tool failed. The Admin tool is not fully supported. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An exception was created during handler fault processing. |
Action | Inspect your handlers. |
Explanation | The Web services engine cannot locate or load the indicated class. |
Action | Determine why the class was not found or loaded. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The handler is missing a response. |
Action | 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/ . |
Explanation | The handler is missing a response. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The handler tried to illegally manipulate xml. |
Action | Correct your handler. |
Explanation | The handler cannot call this method in a managed container. |
Action | Correct your handler. |
Explanation | The handler cannot call this method in a managed container. |
Action | Correct your handler. |
Explanation | This error message indicates a deployment error. |
Action | 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/ . |
Explanation | This error message likely indicates an internal problem. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The protocol for a JMS URL string should be jms: |
Action | Make sure that a proper Java Message Service (JMS)-based URL is passed to the JMSURLParser constructor when the object is constructed. |
Explanation | The set of properties currently contained within the JMSURLParser object cannot form a valid JMS-style URL string. |
Action | Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed. |
Explanation | An internal error has occurred. |
Action | 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/ . |
Explanation | The value supplied for the specified property was not correct. |
Action | Make sure that you use the correct value for the specified property. |
Explanation | A request did not complete within the specified timeout period. |
Action | Make sure that your server is active and is able to process requests within the allotted time. |
Explanation | The Java Message Service (JMS) correlation ID in the reply message did not match the JMS message ID in the request message. |
Action | 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/ . |
Explanation | The Java Message Service (JMS) reply message must be the javax.jms.BytesMessage type. However, the reply message is a different type. |
Action | 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/ . |
Explanation | To allow overloaded operations would cause duplicate xsi types of the same name. |
Action | Use a different combination of Java2WSDL emitter options. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The run time set a response message onto the MessageContext for a one-way message. |
Action | Correct the JAXRPC Handler logic. |
Explanation | An exception was created during handler fault processing. |
Action | Inspect your handlers and correct as needed. |
Explanation | It's not allowed to set a value for the node as described in the exception. |
Action | Correct your application code. |
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. |
Action | Fix the Web Services Description Language (WSDL) file. |
Explanation | The specified interface must subclass 'javax.xml.rpc.Service'. |
Action | Specify an interface that subclasses 'javax.xml.rpc.Service'. |
Explanation | The object cannot be instantiated. An exception may have been logged. |
Action | Contact the provider of the object which cannot be instantiated to determine the cause of the exception. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This property maps to a boolean value |
Action | 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/ . |
Explanation | xsd:list itemTypes must be atomic values. |
Action | Correct the Web Services Description Language (WSDL) file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The runtime does not receive any HTTP Basic Authentication information from the prompt, or the loginSource property is not configured. |
Action | Make sure that you specify the user ID and password at the prompt. You also can see the product documentation for information on how to configure the loginSource property. |
Explanation | A previous version of the deployment descriptor file exists where a new deployment descriptor will be written. The previous version will be overwritten. |
Action | If this process is not expected, check your deployment descriptor versions. |
Explanation | A previous version of the deployment descriptor file exists where a new deployment descriptor will be written. The previous version will be overwritten. |
Action | If this process is not expected, check your deployment descriptor versions. |
Explanation | The Web services engine expected a valid CharacterEncoding value for the incoming message. |
Action | Correct the CharacterEncoding value for the incoming message. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | Examine the exception stack trace for more detail. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The SOAP message does not contain a date/time value. |
Action | Ensure that the date/time value in the SOAP message contains a valid value. |
Explanation | The SOAP message does not contain a time value. |
Action | Ensure that the time value in the SOAP message contains a valid value. |
Explanation | The SOAP message does not contain a date value. |
Action | Ensure that the date value in the SOAP message contains a valid value. |
Explanation | The specified service locator is not a subclass of the service interface. |
Action | Specify a service locator that is a subclass of the specified service interface. |
Explanation | The contents of the SOAP body should have been decrypted by the Web services security functionality. |
Action | 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/ . |
Explanation | The mapping file is used to describe the Java mappings for XML qualified names (QNames). In this case, the QName is incorrect or cannot be located. The corresponding information in the mapping file has been ignored. |
Action | If this mapping file was created by non-IBM tooling, please contact the vendor. |
Explanation | The mapping file is used to describe the Java mappings. In this case, the java-xml-type-mapping is missing. The exception-mapping construct is ignored. |
Action | If this mapping file was created by non-IBM tooling, please contact the vendor. |
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 the invokeOneWay method there is never output. |
Action | Call the Call.invoke method before calling the Call.getOutputParams or Call.getOutputValues methods. |
Explanation | The JAX-RPC application programming interface (API) is not used properly in the handler. |
Action | Review and correct the use of the JAX-RPC APIs. |
Explanation | The JAX-RPC application programming interface (API) is not used properly in the handler. |
Action | Review and correct the use of the JAX-RPC APIs. |
Explanation | The JAX-RPC application programming interface (API) is not used properly in the handler. |
Action | Review and correct the use of the JAX-RPC APIs. |
Explanation | A Web services request was made which involves the JMS transport, but the request does not include a valid endpoint address URL. |
Action | 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. |
Explanation | The Web services engine cannot obtain a secure socket factory using the Secure Sockets Layer (SSL) settings of Java Secure Sockets Extension (JSSE). |
Action | Verify your JSSE SSL setting if you intend to use JSSE SSL setting for the SSL configuration. |
Explanation | This message provides the configured HTTP proxy information. |
Action | No action is required. |
Explanation | This message provides the configured HTTPS proxy information. |
Action | No action is required. |
Explanation | This message provided information about the specified Secure Sockets Layer (SSL) configuration. SSL can be configured using a Java property file, a SSL configuration alias, or the Java Secure Sockets Extension (JSSE) SSL settings. |
Action | No action is required. |
Explanation | This message describes the HTTP response from the Proxy for the HTTP CONNECT request. |
Action | No action is required. |
Explanation | Attempt has been made to generate the code without first parsing the Web Services Description Language (WSDL) file. |
Action | 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/ . |
Explanation | The WSDL2Java emitter issues this message when it has attempted to write data to a file and the attempt was denied by underlying file operating system. This error most likely occured due to restrictions with the application developer. |
Action | No action is required. |
Explanation | The Web Services Interoperability Organization (WS-I) mandates that the style and use settings for inputs, outputs, and faults settings must match in any one binding. For more information, see the WS-I Web site at the following address: http://www.ws-i.org/ |
Action | Modify your Web Services Description Language (WSDL) document to make that the style and use settings for inputs, outputs, and faults are consistent. |
Explanation | The -javaSearch option of WSDL2Java emitter is incorrect. |
Action | Correct the -javaSearch option setting by using a valid option. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The Web Services Description Language (WSDL) file has a relative namespace, such as /home. The file does not have ancestor absolute namespaces to pre-catenate and make an absolute namespace, such as http://www.ibm.com/home. |
Action | Fix the namespaces in the WSDL file. |
Explanation | A validation error occurred. A return type for an existing service endpoint interface classis not compatible with its Web Services Description Language (WSDL) definition. |
Action | Correct the incompatibility between your existing service endpoint interface and the WSDL document. |
Explanation | A validation error occurred. A parameter type for an existing service endpoint interface class is not compatible with its Web Services Description Language (WSDL) definition. |
Action | Correct the incompatibility between your existing service endpoint interface and the WSDL document. |
Explanation | A validation error occurred. An existing Java class field type is not compatible with it Web Services Description Language (WSDL) definition. |
Action | Correct the incompatibility between your existing Java class and WSDL document. |
Explanation | A validation error occurred. An existing enumeration class is missing a required method. |
Action | Add the specified method to the enumeration class. |
Explanation | A validation error occurred. An existing enumeration class contains a method that is not valid. |
Action | Remove specified method from the Enumeration class. |
Explanation | A validation error occurred. An existing Bean class does not contain required default constructor. |
Action | Add a default constructor to the specified Bean. |
Explanation | A validation error occurred. The specified bean class does not extend the appropriate Java class. |
Action | Change the specified bean class to extend a compatible Java class. |
Explanation | A validation error occurred. The specified bean does not have the corresponding bean properties for its data members. |
Action | Make the data member public or add the corresponding get and set methods. |
Explanation | A validation error occurred. The specified fault class is not a Java exception class. |
Action | Make the specified fault class extend the java.lang.Exception class. |
Explanation | A validation error occurred. The specified fault class does not implement a constructor with the correct number of parameters. |
Action | Make sure that the fault class implements a public constructor with the required parameters. |
Explanation | A validation error occurred. The specified fault class does not have the corresponding bean properties for its data members. |
Action | Make the data member public or add the corresponding get and set methods. |
Explanation | A validation error occurred. An existing fault class parameter type is not compatible with its Web Services Description Language (WSDL) definition. |
Action | Correct the incompatibility between your existing fault class and the WSDL document. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The Java2WSDL emitter has encountered a duplicate binding. |
Action | No action is required. |
Explanation | The emitter is attempting to help by doing this conversion. |
Action | No action is required. |
Explanation | An unsupported binding type has been requested. |
Action | Ensure that only valid binding types are requested. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Java2WSDL emitter -location option was not specified. |
Action | No action is required unless a location other than the default is desired. |
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 <binding-type>.location properties instead of using the -location command-line option. |
Action | Specify multiple endpoint location URI values with the -properties option. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The specified property is required. |
Action | Specify the required property. |
Explanation | See the previously reported errors. |
Action | Fix the cause of previously reported, associated errors. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The Web Services Description Language (WSDL) file cannot be found where it was expected. |
Action | Fix the WSDL file within the exterprise archive (EAR) file. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | The ClassLoader parameter is required for the method to function properly, but a null value was passed in. |
Action | Ensure that a non-null value is passed in for the ClassLoader parameter. |
Explanation | An internal error occurred. |
Action | 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/ . |
Explanation | Either the SOAPElement does not contain a text node or the text node does not refer to an attachment. |
Action | Make sure the SOAPElement is a swaRef element by calling the isSwaRef method. |
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 |
Action | Make sure that the parameters for the addSwaRefTextNode method are consistent. |
Explanation | The file that has been specified by user cannot be found in the file system. |
Action | Make sure that file exists and that the file name is spelled correctly. |
Explanation | The imported file that is specified in Web Services Description Language (WSDL) file cannot be located in the file system. |
Action | Make sure that the file exists and that the file name is spelled correctly. |
Explanation | The document and encoded combination is not a valid combination of style and use. |
Action | Use a valid combination of style and use such as rpc/encoded, rpc/literal, or document/literal. |
Explanation | The document and encoded combination is not a valid combination of style and use. |
Action | Use a valid combination of style and use such as rpc/encoded, rpc/literal, or document/literal. |
Explanation | This message specifies the configured syncTimeout value in seconds. |
Action | No action is required. |
Explanation | This message is for informational purposes. |
Action | No action is required. |
Explanation | This message is for informational purposes. |
Action | No action is required. |
Explanation | This message indicates the HTTP response from the server. |
Action | No action is required. |
Explanation | The HTTP status information is not available to determine the HTTP response. |
Action | Make sure the target HTTP server is up. |
Explanation | The HTTP response indicates a new location for the target resource. |
Action | You may want to check the product documentation for details about how to accept the automatic redirection to the new location. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Failure messages have been received from the Channel Framework service. |
Action | Check the log file for the errors that have been reported by Channel Framework service. |
Explanation | The Web services engine found an unsupported schema with the HTTP transport. |
Action | Verify the target endpoint address. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The run time failed to get the HTTP proxy information to process the proxy connection. |
Action | Make sure that the HTTP or HTTPS proxy information is configured properly. See the product documentation for information on how to configure for HTTP proxy. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Web services engine is sending the current SOAP message over an HTTP request with the indicated HTTP version. This message is for informational purposes only. |
Action | No action is required. |
Explanation | An unsupported HTTP version has been detected. This is an internal error. |
Action | 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/ . |
Explanation | The HTTP response is not valid. This error is an internal error. |
Action | 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/ . |
Explanation | Failures have occurred with the HTTP Channel service. |
Action | Check the log file for the errors that have been reported by HTTP Channel service. |
Explanation | Failures have occurred with the SSL Channel service. |
Action | Check the log file for the errors that have been reported by SSL Channel service. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message indicates how many keystore password properties have been identified. |
Action | No action is required. |
Explanation | An attempt has been 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. |
Action | Correct the data being serialized. |
Explanation | When you append /wsdl to a service URL it is a request to retrieve a Web Services Description Language (WSDL) document that contains SOAP ports for the HTTP or JMS transports. If the ports do not exist, this error is displayed instead of the WSDL document. |
Action | Modify the query to obtain the extended WSDL document or contact the Web service owner. |
Explanation | The engine or tool failed to parse the CustomBindingProvider.xml to build the CustomProvider object. |
Action | Check the CustomBindingProvider.xml files to see whether there are any syntax error. |
Explanation | The Web services engine expects that every custom type mapping has a non-default namespace. |
Action | Correct the CustomBindingProvider.xml file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A validation error occurred. The specified bean class does not extend the same extension base that is specified in the Web Services Description Language (WSDL) document. |
Action | Change the specified bean class or the WSDL document to extend the appropriate Java class. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The run time found an unknown outbound connection object. This problem might be an internal error. |
Action | Check for a connection exception in the log file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Web services engine attempted to access a closed connection. This problem might be an internal error. |
Action | Check for a connection exception in the log file. |
Explanation | An exception has caused the release of a saved virtual connection object and an outbound service context. |
Action | Check the log for the last exception that was caught. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This WSDL2Java emitter error indicates that an attribute is referenced but it cannot find a definition. |
Action | Correct your Web Services Description Language (WSDL) file so that the appropriate definition is located. |
Explanation | Based on a Java system property setting, each HTTP connection is retried until the connection succeeds. However, this action is not recommended as a deadlock might occur. |
Action | Consider modifying the configuration of the target's HTTP inbound transport to accept more connections. |
Explanation | Based on a Java system property setting, each HTTP connection is retried for the configured number of times. However, be cautious about changing this property as a deadlock might occur. The default value is 3. |
Action | Consider modifying the configuration for the target HTTP inbound transport to accept more connections. |
Explanation | The reported exception is caught, but the HTTP connection will be retried until the configured number of times is reached. |
Action | Consider modifying the configuration for the target HTTP inbound transport to accept more connections. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An internal discovery problem occurred that might be related to the class loader. |
Action | 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/ . |
Explanation | An internal discovery problem occurred that might be related to the class loader. The WSDL2Java emitter cannot continue. |
Action | 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/ . |
Explanation | A bad property has been detected on the MessageContext or OperationDesc. This problem might be caused by an internal error. |
Action | 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/ . |
Explanation | A bad property has been detected on the MessageContext or OperationDesc. This problem might be caused by an internal error. |
Action | 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/ . |
Explanation | Either the above custom binder does not exist or it is not in the class path for the context classloader. |
Action | 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/ . |
Explanation | The -MIMEstyle option of the Java2WSDL emitter is incorrect. |
Action | Use the correct -MIMEstyle option. The value must be AXIS, swaRef, or WSDL11. |
Explanation | This WSDL2Java emitter error indicates that a group is referenced, but a definition cannot be found. |
Action | Correct the Web Services Definition Language (WSDL) file. |
Explanation | This WSDL2Java emitter error indicates that a attributeGroup value is referenced, but a definition cannot be found. |
Action | Correct the Web Services Definition Language (WSDL) file. |
Explanation | Compression is not 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. |
Action | You can complete one of the following actions 1.) Validate the value of Web services property for HTTP compression. 2.) Check for error messages from the HTTP Channel. 3.) Ignore the message if compression is not needed. |
Explanation | This message indicates whether the described compression type is enabled. Note: gzip and x-gzip compression use the same compression mechanism. |
Action | Verify that the Web services property for HTTP compression is configured as needed. |
Explanation | This message indicates whether the deflate compression type is enabled. |
Action | Verify that the Web services property for HTTP compression is configured as needed. |
Explanation | This message specifies the type of HTTP Channel that is used for HTTP connection. It could be an In-process or network type. |
Action | No action is required. |
Explanation | There might be an error when the system attempted to find an Inprocess HTTP Channel. However, this message might not be a problem unless an in-process connection is required. The system continues with a channel network type instead. |
Action | If necessary, check the trace for Work Load Management (WLM) or Dynamic Work Load Management Client (DWLMclient) errors. |
Explanation | The printed data has been used to map to a valid cluster name. |
Action | No action is required. |
Explanation | The -wrapped option is only applicable if -use LITERAL and -style DOCUMENT. |
Action | Remove the -wrapped option or set the -use/-style options correctly. |
Explanation | This message lists the value that is set by the Web services client for acceptable content-codings in the HTTP response. For more details, see the Hypertext Transfer Protocol specification. A null header value indicates an empty Accept-Encoding header in the incoming HTTP request; hence, content encoding is not done in the HTTP response. |
Action | If this is a Web services client, check the Web services property for HTTP compression encoding of the target service port. Make sure that the value is configured properly. |
Explanation | This printed data is used to map for a channelframework endpoint object that can be used later to create In-process connection. |
Action | No user action is required. |
Explanation | The specified endpoint has beens used to invoke the Service.getPort method. |
Action | Correct the invocation of the Service.getPort method. |
Explanation | The specified port has been used to invoke the Service.createCall method. |
Action | Correct the invocation of the Service.createCall method. |
Explanation | The specified operation has been used to invoke the Service.createCall method. |
Action | Correct the invocation of the Service.createCall method. |
Explanation | A validation error occurred. The specified bean does not correctly define a bean property for the designated data member. |
Action | Make the data member public or add an appropriate set method. Be particularly careful to ensure that the get and set methods use the same capitalization. |
Explanation | Informational message about what was received as a Web services request. |
Action | No action is required. |
Explanation | Informational message about what was received in response to a previous Web services request. |
Action | No action is required. |
Explanation | Informational message about what was sent as a Web services request. |
Action | No action is required. |
Explanation | Informational message about what was sent as a response to a Web services request. |
Action | No action is required. |
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. |
Action | If Clustering is used, check for errors from Dynamic Work Load Management Client(DWLMClient) in trace. |
Explanation | Fatal errors have been encountered most likely due to user error. For more information, see the associated error messages. The code and artifacts generation has been suspended. |
Action | Correct the reported problems and try again. |
Explanation | The Web services engine attempted to protect the SOAP message body before invoking the JAX-RPC handlers. However, an unknown error occurred in the process. |
Action | 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/ . |
Explanation | The JSR109 mapping file defined a name for the XML construct that is different than the default mapping. |
Action | No action is required. |
Explanation | The custom binder defined a name for the XML construct that is different than the default mapping. |
Action | No action is required. |
Explanation | Java reflection indicates that the name of the XML construct is different than the default mapping. |
Action | No action is required. |
Explanation | The Web services engine is performing introspection of the indicated SEI. |
Action | No action is required. |
Explanation | The Web services engine is performing introspection of the indicated class. |
Action | No action is required. |
Explanation | A portType operation within the Web Services Description Language (WSDL) file is not valid. |
Action | Correct the WSDL file. |
Explanation | When the property is specified, the corresponding property also must be specified. |
Action | Re-specify the property using bindningTypes http. |
Explanation | When the property is specified, the corresponding property must also be specified. |
Action | Re-specify the property using bindningTypes jms. |
Explanation | When the property is specified, the corresponding property must also be specified. |
Action | Re-specify the property using bindingTypes ejb. |
Explanation | An inconsistent portType and binding operation have been encountered in the Web Services Description Language (WSDL) file. |
Action | Make sure that the WSDL file is correct. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The indicated identity object has been received from the WS-Addressing functionality. If the object is null, the transport attempts to map one by the RequestMapper. |
Action | If clustering is used, check for errors from the WS-Addressing functionality in the trace. |
Explanation | The indicated identity object cannot be mapped to a valid endpoint. |
Action | If the object is null, check for errors from Clustering and ChannelFramework functionality in the trace. |
Explanation | An exception has been caught. However, the exception can be benign because the transport can proceed to next option using the RequestMapper to resolve the endpoint. |
Action | If applicable, check for errors that are related to the WS-Addressing functionality. |
Explanation | An exception has been caught. However, the exception can be benign because the transport can proceed to next option using the default channels to resolve the endpoint. |
Action | If applicable, check for errors that are related to the Dynamic Work Load Management Client. |
Explanation | The service endpoint implementation has created an exception. This message might indicate an error in the service endpoint implementation. |
Action | Contact the owner of the service endpoint implementation to determine if this exception indicates normal processing or an error condition. |
Explanation | This error message is likely a symptom of an incorrect Web Services Description Language (WSDL) file. |
Action | Fix the WSDL file to remove the ambiguity. |
Explanation | The Document/Literal operations must have unique parameter elements in their input message so that the target server can determine which operation is invoked. |
Action | Fix the Web Services Description Language (WSDL) file to remove the ambiguity. |
Explanation | The Document/Literal operations must have unique parameter elements in their input message so that the target service can determine which operation is invoked. |
Action | Specify the -wrapped true option on the Java2WSDL emitter. |
Explanation | This informational message describes the current condition of the outbound HTTP connection pool. |
Action | No action is required. |
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. |
Action | 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. |
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. |
Action | 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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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. |
Action | Consider increasing the connection wait timeout, and increasing the maximum connections value. Check for network problems. |
Explanation | This message originates from the outbound connection cache of the channel transport. |
Action | 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/ . |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The indicated construct cannot have mixed character content. |
Action | Correct the SOAP message. |
Explanation | An unexpected exception occurred and the run time has detected generated code that is from a different build. |
Action | Deploy your application again with the wsdeploy command. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
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. |
Action | Correct the client message so that it matches the style that is expected on the server. |
Explanation | The parameters in the SOAP message must be unique. |
Action | Change the part name for the Web Services Description Language (WSDL) message and the element attributes to ensure unique parameters. |
Explanation | The input service endpoint interface references a class that is nested inside another class. This process is unsupported. |
Action | Change the Java structure. |
Explanation | The emitter has found a non-Web Services Description Language (WSDL) or schema document that is being referenced through a wsdl:import. |
Action | Make sure that the document that is being imported is a valid Web Services Description Language (WSDL) document. You can use the WSDL:imports to import a schema, but it is not recommended. |
Explanation | The emitter found that a wsdl:import namespace attribute is being used to import a schema document instead of a Web Services Description Language (WSDL) file. |
Action | To be compliant with the Web Services Interoperability (WS-I) specification, make sure that the wsdl:imports namespace attribute only imports WSDL documents and that the xsd:imports statement is used instead to import schemas. |
Explanation | A wsdl:import namespace attribute contains a relative URI, which is not compliant with the Web Services Interoperability (WS-I) specifications. |
Action | To be WS-I compliant you must make the namespace attribute an absolute URI, such as http://www.ibm.com/home. |
Explanation | The schemaLocation attribute of the xsd:import does not resolve to a document whose root element is a schema. This situation does not comply with Web Services Interoperability (WS-I) specifications. |
Action | To be WS-I compliant, you must make sure that the schemaLocation attribute resolves to a document whose root element is a schema. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | A connection to the remote host was not possible. |
Action | Check the connection and port settings. For more information, review the reported errors. |
Explanation | A schema import, include, or redefine is not being defined within an xsd:schema element. This situation does not comply with Web Services Interoperability (WS-I) specifications. |
Action | To be WS-I compliant, make sure the schemas are imported, included, or redefined from within schema elements. Use the Web Services Description Language (WSDL) imports function from within a WSDL definition document. |
Explanation | A wsdl:import statement is missing the location attribute. Processing cannot continue. |
Action | Add the location attribute to the specified wsdl:import element. |
Explanation | The specified Web Services Description Language (WSDL) document is not Web Services Interoperability (WS-I) compliant as it does not preserve the element order, which is specified by the WS-I specifications. The WS-I specifications state that wsdl:import elements must precede all of the other elements from the WSDL namespace except the wsdl:documentation element. |
Action | To be WS-I compliant, change the order of the WSDL elements definitions and make sure that the wsdl:import elements are preceded by the wsdl:documentation, wsdl:#comment or wsdl:#text elements only. |
Explanation | The specified Web Services Description Language (WSDL) document is not Web Services Interoperability (WS-I) compliant as it does not preserve the element order that is specified by the WS-I specifications. The WS-I specifications state that wsdl:types elements must precede all of the other elements from the WSDL namespace except the wsdl:documentation and wsdl:import elements. |
Action | To be WS-I compliant, change the order of the wsdl elements that are defined and make sure that the wsdl:types elements are preceded by the wsdl:documentation, wsdl:#comment, wsdl:#text or wsdl:import elements only. |
Explanation | The namespace attribute of the wsdl or xsd import function is not defined and the file being imported does not contain a targetNamespace definition. Thus, this configuration is not supported. |
Action | Make sure that both, the namespace attribute and the targetNamespace definition for the imported file, are defined and equal in value. |
Explanation | The Web Services Interoperability (WS-I) specification requires import namespace attributes to equal the value of the targetNamespace value for the imported document. |
Action | Make sure that both, the namespace attribute and the targetNamespace definition for the imported file, are defined and equal in value. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | To set implicit SOAP headers on a Stub or Call object, you must use a java.util.HashMap. |
Action | Correct the client application code. |
Explanation | To set implicit SOAP headers on a Stub or Call object, you must use a non-empty java.util.HashMap. |
Action | Correct the client application code. |
Explanation | The java.util.HashMap used with implicit SOAP headers should contain a non-null key of type javax.xml.namespace.QName. |
Action | Correct the client application code. |
Explanation | The java.util.HashMap used with implicit SOAP headers contained a key of the incorrect type. |
Action | Correct the client application code. |
Explanation | The java.util.HashMap containing request SOAP headers should contain non-null values. |
Action | Correct the client application code. |
Explanation | The java.util.HashMap containing request SOAP headers should contain values of type "java.lang.String" or "javax.xml.soap.SOAPElement". |
Action | Correct the client application code. |
Explanation | The java.util.HashMap containing response SOAP headers should contain null values. |
Action | Correct the client application code. |
Explanation | The client application attempted to set or get an implicit SOAP header that has been declared as protected. |
Action | Do not attempt to set or get a protected SOAP header. |
Explanation | A validation error was found in the request SOAP header HashMap, yet the HashMap should have been validated previously. This is an internal error. |
Action | 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/ . |
Explanation | This operation is not supported by the SOAP with Attachments API for Java (SAAJ) Version 1.2 specification. |
Action | Please use a DOM 2 API. |
Explanation | The -deployScope option modifies the output only when the is role develop-server. |
Action | Correct the option setting. |
Explanation | An unexpected exception was caught during the dispatching of the message. |
Action | Determine the source of the exception using the class name of the dispatcher and the call stack that is presented in the message. If the exception is from an external provider, contact the provider for a resolution. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The WSDL2Java emitter does not support redefine elements with extensions. |
Action | Correct your Web Services Description Language (WSDL) file or schema. Completely define the type within the redefine element. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The run time has found Secure Sockets Layer (SSL) properties programmatically set on the current thread. The same properties are registered with the event listener. SSL properties that are programmatically set always have the highest precedence. |
Action | If this precedence is not intended, the application should not programmatically set the properties prior to invocation. |
Explanation | Based upon the JAX-RPC model, the Secure Sockets Layer (SSL) configuration alias or SSL certificate alias can be specified and might have been found from the message context. The information is used for the SSL connection of the current invocation. However, there might not be value for each alias if the alias has never been specified. |
Action | If this scenario is not intended, the application should not set the properties prior to invocation. For more information, see the product documentation. |
Explanation | The runtime failed to resolve for an effective SSL configuration. Attempt to default to the JSSE system properties. |
Action | Make sure the SSL configuration is properly set for this invocation following the precedence rules specified in the product documentation. |
Explanation | The runtime failed to resolve for an effective SSL configuration with the specified endpoint. |
Action | Make sure SSL configuration is properly set for this endpoint following the precedence rules specified in the product documentation. |
Explanation | The Secure Sockets Layer (SSL) properties have been received from the security configuration. The same properties are registered with the event listener. |
Action | No action is required. |
Explanation | Internal operation. |
Action | No action is required. |
Explanation | Internal operation. The connection object marked is not usable. |
Action | No action is required. |
Explanation | Internal operation. The connection object invalidated is not usable. |
Action | No action is required. |
Explanation | Internal operation. |
Action | No action is required. |
Explanation | This exception might be due to a timing problem that is caused by the asynchronous operation, which is done by the Unified Clustering Framework. The Web services engine will attempt to query from the Unified Clustering Framework again. |
Action | No action is required. |
Explanation | The second query has failed. The Web services engine proceeded to the next option using default channels. |
Action | If unified clustering is needed, this message is an error. Check the trace for any errors from the clustering functionality. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The application uses a type that is not a JAX-RPC supported type. Although the Web services engine proceeds with generating artifacts, it's use is not supported. |
Action | Modify your application to use a type that is not a java.util.Collection type, use custom data mappings to map the Collection type, or use it as-is, at your own risk. |
Explanation | A new WS-Addressing destination endpoint reference (EPR) is being set. However, the service name from the EPR does not match the original service name that is configured in this object. |
Action | Enable WS-Addressing trace and check for WS-Addressing errors. |
Explanation | Standard IBM Copyright. |
Action | No action is required. |
Explanation | Standard IBM banner displayed by the web services emitter. |
Action | No action is required. |
Explanation | Standard IBM banner displayed by the Java to WSDL emitter. |
Action | No action is required. |
Explanation | Standard IBM banner displayed by the WSDL to Java emitter. |
Action | No action is required. |
Explanation | The HTTP host value is not valid. This error might be an internal error. |
Action | Modify or add valid host to the endpoint URL. |
Explanation | The HTTP port value is not valid. This error might be an internal error. |
Action | Modify or add valid port to the endpoint URL. |
Explanation | This message provides information about the local and mapped cell names. The mapped cell name can be from a remote cluster. |
Action | No action is required. |
Explanation | The Web services engine is unable to evaluate the current endpoint reference (EPR) in the WS-Addressing run time. |
Action | Make sure that the EPR is set properly. Enable WS-Addressing trace for more information. |
Explanation | This message states that the sendSOAPRequestAsync method is used to make a re-directed asynchronous delivery. This situation occurs only with re-directed asynchronous delivery due to WS-Addressing. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message tracks the response that is received for the previous asynchronous delivery that is caused by WS-Addressing. This message is for informational purposes only. |
Action | No action is required. |
Explanation | An error has occurred in the previous asynchronous delivery that is caused by WS-Addressing. |
Action | Review the associated exception messages that occur after this message. |
Explanation | A new WS-Addressing destination endpoint reference (EPR) is being set. However, the port name from the EPR does not match the original port name that is configured in this object. |
Action | Enable WS-Addressing trace and check for WS-Addressing errors. |
Explanation | The WSDL2Java emitter does not currently support XML schema substitution groups. Any reference to a substitution group is ignored. |
Action | Modify your Web Services Description (WSDL) file or do not expect substitution group designations in the generated artifacts. |
Explanation | The Java2WSDL emitter only uses qualified or unqualified for the elementFormDefault option. |
Action | Modify your Java2WSDL invocation to include a valid argument for the elementFormDefault option. |
Explanation | The Java2WSDL emitter only uses qualified or unqualified for the attributeFormDefault option. |
Action | Modify your Java2WSDL invocation to include a valid argument for the attributeFormDefault option. |
Explanation | The WSDL or schema file contains relative namespaces, such as "/home". |
Action | When you use relative namespaces, you may have problems interoperating with other vendors and will encounter security limitations. Consider converting the relative namespaces to absolute namespaces. |
Explanation | This option or property is not recognized by the emitters. The tooling will ignore it. |
Action | Check the spelling or case used for the properties names and values and correct any errors. |
Explanation | The WSDL2Java emitter encountered an unsupported binding namespace and will continue code generation process for the supported binding(s). |
Action | To avoid this warning, remove unsupported binding namespace from WSDL file. |
Explanation | The SOAP Envelope must be the root element of the message. |
Action | Correct the message to be compliant with Web services interoperability standards or work with your Web services provider. |
Explanation | A Java Message Service (JMS) endpoint URL string must contain the following properties: jndiConnectionFactoryName, targetService. These properties are used to describe the jndi connection factory and target service. |
Action | Correct the JMS endpoint URL and retry. |
Explanation | A Web services request was made which involves the JMS transport, but the request does not start with jms or jms:jndi for the JMS endpoint address URL. |
Action | Make sure that the request contains a valid JMS endpoint address URL. If this request was invoked within the Web Services Gateway, make sure the proper configuration has been done. |
Explanation | The specified JMS endpoint URL string did not contain a valid destination name following the "jms:jndi:" prefix. |
Action | Correct the JMS endpoint URL and retry. |
Explanation | The behavior of SOAPMessage.getSOAPHeader and getSOAPBody methods changed to thrown an exception rather than return null. |
Action | If receiving an exception rather than returning null is acceptable, the do nothing. If you prefer to receive a null then you may do either of the following: 1) Use SOAPMessage.getSOAPPart().getEnvelope().getHeader() or .getBody() as appropriate, or 2) set the System Property com.ibm.websphere.webservices.soap.enable.legacy.get.behavior to true to have the SOAPMessage methods return null rather than throwing an exception. |
Explanation | The indicated method requires SOAP with Attachments API for Java (SAAJ) Version 1.3 support. This support is not available in the the installed version of product. |
Action | Use an SAAJ Version 1.2 method or upgrade to a new version of the product. |
Explanation | The indicated method requires a Document Object Model (DOM) Level 3, which is part of the SOAP with Attachments API for Java (SAAJ) Version 1.3 support. This method is not available in the installed version of the product. |
Action | Use a DOM Level 2 method or upgrade to a new version of the product. |
Explanation | The request information is not available when the SOAPConstants.DYNAMIC_SOAP_PROTOCOL is used. |
Action | Create the SOAP messaage with a SOAP Version 1.1 or SOAP Version 1.2 protocol. |
Explanation | The indicated method is only valid for the SOAP 1.2 protocol. This requirement is defined by the SOAP with Attachments API for Java (SAAJ) Version 1.3 specification. |
Action | Use a method that is valid for your SOAP protocol. |
Explanation | The indicated protocol requires SOAP with Attachments API for Java (SAAJ) Version 1.3 support. This support is not available in the the installed version of the product. |
Action | Use the SOAP Version 1.1 protocol or upgrade to a new version of the product. |
Explanation | Some iterators do not support the remove() method. You cannot call this method on the indicated iterator. |
Action | Do not use the remove method on the iterator. |
Explanation | This behavior is defined by the javax.xml.soap.SOAPFault.getFaultReasonText(Locale) method. |
Action | Inspect your logic for errors. |
Explanation | This behavior is defined by the javax.xml.soap.SOAPFault interface. |
Action | Inspect your logic for errors. |
Explanation | This behavior is defined by the javax.xml.soap.SOAPFault interface. |
Action | Inspect your logic for errors. |
Explanation | The method is only supported for SOAP 1.1 Protocol and SOAP 1.2 Protocol. |
Action | Use the correct protocol. |
Explanation | The specified method cannot be called if the SOAPConstants.DYNAMIC_SOAP_PROTOCOL is used. |
Action | Use the SOAP 1.1 or SOAP 1.2 protocol. |
Explanation | The specified namespace does not match a URI associated with the specified protocol. |
Action | You may have a problem with your SOAP message. |
Explanation | The specified protocol is not a recognized protocol. |
Action | Use one of the following protocols javax.xml.soap.SOAPConstants.SOAP_1_1_PROTOCOL, javax.xml.soap.SOAPConstants.SOAP_1_2_PROTOCOL, or javax.xml.soap.SOAPConstants.DYNAMIC_SOAP_PROTOCOL. |
Explanation | The specified method is not a supported on the specified object. |
Action | Correct your code. |
Explanation | The method requires that the body contain exactly one element. |
Action | Correct your code. |
Explanation | The engine uses the CONTENT_TYPE to determine whether the message is a SOAP 1.1 or SOAP 1.2 message. |
Action | Correct the inbound message. |
Explanation | The SOAP with Attachments API for Java (SAAJ) Version 1.3 interface requires that the prefix is bound. This requirement means that a namespace declaration must exist in an ancestor element. |
Action | Correct the code that called the addChildElement element. |
Explanation | The SOAPEnvelope and SOAPMessage must have the same protocol. |
Action | 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/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | SAAJ requires that certain values, including Fault Code, Fault Subcode, and Headers be namespace qualified. |
Action | Correct the value. |
Explanation | SAAJ 1.3 requires that the Fault Code must be one of the fault codes defined in the version of SOAP specification in use. |
Action | Correct the Fault Code. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The endpoint at this URL has been disabled for requests. Other endpoints within the service may still be running. |
Action | To allow the endpoint to receive requests, enable the endpoint either through wsadmin or admin console. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Action | 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/ . |
Explanation | The JMSSender did not set the correct property on the JMS request message prior to sending the message to the destination queue or topic. This is an internal error. |
Action | 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/ . |
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. |
Action | 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/ . |
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. |
Action | 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/ . |
Explanation | The JMSSender did not set the correct version on the JMS request message prior to sending the message to the destination queue or topic. This is an internal error. |
Action | 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/ . |
Explanation | An internal system error occurred. Access to the endpoint is still available, but the ability to stop the listener for this endpoint has been disabled. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |