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 | Please specify the -location option. |
Explanation | The -server-side option is incorrect. |
Action | Please specify the correct -server-side option. |
Explanation | The -transport option is incorrect. |
Action | Please specify the correct option. |
Explanation | This pre-existing operation has an output element. It is removed. |
Action | None. |
Explanation | This pre-existing operation has a fault element. It is removed. |
Action | None. |
Explanation | Loading specified class. |
Action | None. |
Explanation | Generating indicated construct. |
Action | None. |
Explanation | A JMS endpoint URL must specify either 'queue' or 'topic' as the destination type. |
Action | Correct the JMS endpoint URL and re-try. |
Explanation | A JMS endpoint URL string contained an unrecognized property. |
Action | Correct the JMS endpoint URL and re-try. |
Explanation | A JMS endpoint URL string must contain the following properties: connectionFactory, destination, targetService. These properties are used to describe the destination queue or topic and target service. |
Action | Correct the JMS endpoint URL and re-try. |
Explanation | An error occurred while trying to create a JNDI InitialContext object. |
Action | Use the detailed information in the original error message to determine the problem. |
Explanation | The specified error occurred during a JNDI 'lookup' operation. |
Action | Ensure that the JNDI name is correct. |
Explanation | A 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 | None. |
Action | None. |
Explanation | The specified exception occurred while 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. |
Action | Use the detailed information in the original error message to determine how to correct the problem. |
Explanation | The Web services message-driven bean listener was unable to retrieve a configured server engine during its initialization. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Web services JMS listener received a JMS message that was not a TextMessage or a BytesMessage. The JMS listener supports only these two JMS message types. |
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 using a topic. |
Action | Ensure that any services which use topic destinations contain only one-way operations. This means that within the WSDL file, the operation does not contain an 'output' message. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Suspect a bad mapping file supplied to WSDL2Java. |
Action | Correct your mapping file. |
Explanation | The -voidReturn option is incorrect. |
Action | Please specify the correct option. |
Explanation | The message is not a legal SOAP message. |
Action | Contact party that sent this message. |
Explanation | The _Helper class is needed for proper serialization or deserialization. Serialization or deserialization may fail. |
Action | Ensure that the _Helper class was properly emitted by WSDL2Java and deployed correctly. |
Explanation | Some xml constructs cannot be mapped to java types. |
Action | The application code will need to use the SOAPElement methods to construct and analyze the data. |
Explanation | An internal error occurred. Possibly due to an error in the deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The indicated object cannot be serialized. |
Action | Make sure that a proper serializer is registered. |
Explanation | Used either a KeyStore/TrustStore pair or a cryptographic token to get a secure socket factory |
Action | None. |
Explanation | The indicated type cannot be deserialized. |
Action | Make sure that a proper deserializer is registered. |
Explanation | Internal error caused by improper startup code. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original exception. |
Action | Correct Handler code to eliminate RuntimeException. |
Explanation | Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original response message. |
Action | Correct Handler code to eliminate RuntimeException. |
Explanation | The indicated object cannot be serialized. |
Action | Make sure that a proper serializer is registered. |
Explanation | The indicated type cannot be deserialized. |
Action | Make sure that a proper deserializer is registered. |
Explanation | Trying to access a deleted memory managed data source. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The arrayType attribute in the soap message is invalid. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Only Basic authentication is supported with the SimpleServerEngine. |
Action | You should not be using the SimpleServerEngine. |
Explanation | A boolean value in a soap message must be '0', '1', 'true' or 'false'. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A calendar value in a soap message was invalid. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A character in a hex string was invalid. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad date value was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad date/time value was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to deploy the indicated class as a Handler class. However it does not extend the Handler class. |
Action | Correct your deployment information. If 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 | An attempt was made to use the specified class as a Holder. However the class does not extend the Holder interface. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The soap message contains an array that has a non-integer array length. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is normally the result of an internal error in the deployment software. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The envelope element of the soap message has an incorrect namespace. The message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The offset attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal exception of the WSDL2Java emitter. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The position attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | SimpleServerEngine does not understand the request. |
Action | Don't use the SimpleServerEngine. |
Explanation | The argument of the scope option must be Request, Application, or Session. |
Action | Use the proper -scope option when invoking WSDL2Java. |
Explanation | A soap message does not contain an envelope element. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad time value was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad timezone was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A problem has occurred in the deployment software. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is caused by an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This error could be the result of an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | User cannot be authenticated. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | User cannot be authenticated. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | User is not authorized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error: The soap message cannot be converted into bytes. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error: The soap message cannot be converted into a String. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The indicated value could not be assigned to the bean field. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Tool option error. See other messages. |
Action | Fix the URL. |
Explanation | This message normally indicates that the soap message is invalid. The engine was expecting a simple value when it encountered a child element. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The indicated class cannot be serialized 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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 | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Can't make the appropriate tunnel. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Changed passwords on AdminClient. |
Action | AdminClient is not fully supported. |
Explanation | The SAAJ model is being used incorrectly. Please contact the Web services team. if this problem is occurring in the runtime. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | Don't use AdminClient. |
Explanation | Internal Error with deployment software. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The connection is closed. The remote service call cannot be made. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | WSDL2Java issues this message if an different qnames result in the creation of the same java file. |
Action | Fix your wsdl or use the NStoPkg options to differentiate the classes. |
Explanation | The parameter order attribute in the wsdl is incorrect. |
Action | Fix your wsdl. |
Explanation | The endpoint address cannot be found. |
Action | Fix your wsdl. |
Explanation | The endpoint address is invalid. |
Action | Fix your wsdl. |
Explanation | Specify a binding on the service wsdl port. |
Action | Fix your wsdl |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The binding must be defined if referenced. |
Action | Fix the WSDL. |
Explanation | The binding must be defined if referenced. |
Action | Fix the WSDL. |
Explanation | The portType must be defined if referenced. |
Action | Fix the WSDL. |
Explanation | The portType must be defined if referenced. |
Action | Fix the WSDL. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Problem occurred invoking remote Web service. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Admin error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This error could be the result of an invalid soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified directory cannot be read. |
Action | Fix your configuration. |
Explanation | Non performant serialization encountered. |
Action | Examine code and make appropriate changes. |
Explanation | The -container option of WSDL2Java is wrong. |
Action | Fix the option setting. |
Explanation | The -role option of WSDL2Java is wrong. |
Action | Fix the option setting. |
Explanation | The Web service always runs in a web or ejb container. |
Action | Fix the options and rerun WSDL2Java. |
Explanation | This is most likely due to a previous error with the Web services deployment descriptor. |
Action | Review the log for previous errors. |
Explanation | informational message. |
Action | no action required. |
Explanation | The specified service could not be found. |
Action | Check the name of the service specified by the client and the deployment of that service on the server. |
Explanation | A configuration file (was-webservices.xml) defines a handle javaclass that does not implement the expected interface. |
Action | Specify javaclass that implements the expected interface. |
Explanation | The -genJava option of WSDL2Java is wrong. |
Action | Correct the option setting. |
Explanation | The -genXML option of WSDL2Java is wrong. |
Action | Correct the option setting. |
Explanation | Could not get a secure socket factory. |
Action | Correct your SSL configuration. |
Explanation | Error occurred during deployment. This is probably an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This could possibly due to a deserialization error. Look for other errors. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 java.rmi.Remote. |
Action | Fix the invocation of the getPort method. |
Explanation | A password must be supplied. |
Action | AdminClient is not fully supported. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | No user was found to authorize. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Cannot administer remotely. |
Action | The Admin class is not fully supported. |
Explanation | A body was expected in the soap envelope, but was not found. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The array of the indicated component type could not be deserialized. |
Action | This problem may be due to invalid deployment information. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The soap message is invalid and cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally this is the result of bad client or server deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Nornally this is the result of a bad soap message or invalid server deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Probably an Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Invalid configuration data. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error with deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Missing information in deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Missing handlers in deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Header missing in soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The soap message is invalid and cannot be deserialized due to presences of processing instructions. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The object cannot be serialized by the MapSerializer. This is probably the result of an internal deployment error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Deployment information is not complete. This is probably the result of an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The WSDL does not define any operations in the portType. |
Action | This is an internal error or deployment error. |
Explanation | The WDSL binding did not specify the operation. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The indicated option was not found. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The parameter order attribute must reference a message part. |
Action | Correct the WSDL. |
Explanation | The specified port could not be found by Service.getPort. |
Action | Correct the invocation of Service.getPort. |
Explanation | The deployed wsdl is missing the portType. |
Action | Correct the deployed wsdl. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Usually this indicates a internal error with the deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 | Make sure a security provider is configured. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The indicated array component type cannot be serialized. Make sure this type is registered. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The component of the vector cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Missing deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Missing deployment information in the type mapping registry. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Handler did not understand mustUnderstand headers. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Exception. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Processing cannot continue because the indicated item is null. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | AdminClient is not fully supported. |
Explanation | Namespace argument must be specified. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Tried to call SAAJ setParent with a null argument. This may be the result of an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Missing deployment information. This may be the result of an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The HexBinary object cannot be constructed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The soap message contains multiple soap bodies inside the envelope. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The soap message contains multiple soap headers inside the envelope. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The number of parameters does not match the expected number of parameters. |
Action | This could be a DII or internal error. |
Explanation | informational message. |
Action | no action required. |
Explanation | Problem occurred deserializing the soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | AdminClient error processing the indicated file. |
Action | AdminClient is not fully supported. |
Explanation | informational message. |
Action | no action required. |
Explanation | Admin quitting. |
Action | Admin class is not fully supported. |
Explanation | Internal Error. |
Action | SimpleServerEngine not fully supported. |
Explanation | informational message. |
Action | no action required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | /WEB-INF may not be accessible. |
Action | Correct problem with WEB-INF directory. |
Explanation | config file may not be accessible. |
Action | Correct problem with servlet engine config file. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | no action required. |
Explanation | Configuration error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | informational message. |
Action | no action required. |
Explanation | The WSDL part must specify the type or element attribute. |
Action | Correct the deployed wsdl. |
Explanation | Internal Error or problem with input soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unknown host encountered by Admin tool. |
Action | The Admin tool is not fully supported. |
Explanation | Admin tool error. |
Action | Admin tool is not fully supported. |
Explanation | Normally an error with the deployed wsdl detected during service creation. |
Action | Correct the deployed wsdl. |
Explanation | A WSDL document is needed if you want to use Service.getPort. |
Action | Correct your deployment information. |
Explanation | Internal Error in the WSDL2Java SymbolTable. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Your wsdl references types or elements that are not defined. |
Action | Correct your wsdl. |
Explanation | There may be a problem with your 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 | Found recursive definition of the indicated type or element. |
Action | Correct your wsdl. |
Explanation | A bad property detected on the Call or MessageContext. This could be caused by an internal error. |
Action | Fix the property. |
Explanation | A bad property was detected. This could be caused by an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A null property value was specified. This could be caused by an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unsupported property is being used. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is normally due to an internal error associated with the serialization engine. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is normally due to an internal error associated with the deserialization engine. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is normally due to an internal error with the serialization engine. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The isRegistered method requires a non-null java class. This error could be the result of an internal problem. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The isRegistered method requires a non-null qname. This error could be the result of an internal problem. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This error normally suggests a problem with the deployment software. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The WSDL contains unsupported MIME constructs. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The WSDL service name is wrong. |
Action | Correct the WSDL. |
Explanation | Attributes must be simple types. |
Action | Correct the WSDL. |
Explanation | Attributes must be simple types. |
Action | Correct the WSDL. |
Explanation | Problem creating JAXRPC Handler. |
Action | Review reasons for thrown exception. |
Explanation | informational message |
Action | No action required. |
Explanation | This normally indicates a problem with the deployed type mapping registry. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Exception. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Used for various exceptions. See other messages. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Used for various exceptions.. See other messages. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally indicates an internal error has occurred. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Indicates that an error has occurred while configuring the xml 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 indicates that an internal error has occurred. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally indicates a problem with a MIME message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Normally an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This may be issued during overloaded message processing. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | This error may occur during overloaded method processing. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | A problem occurred invoking the indicated target. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | This error may indicate a problem with MIME attachments. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Malformed URL Exception occurred in the SimpleServerEngine. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | A WebServicesFault has occurred. |
Action | See other messages for more detailed information. |
Explanation | informational message. See other messages for details about why the fault was issued. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | informational message. See other messages for details about why the fault was issued. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | Indicates that the WSDL or one of it's imported documents is not accessible. |
Action | Make sure the WSDL and/or any imported documents are accessible. You can also increase the timeout & retry values through the WSDL2Java options. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An operation has been invoked on a Stub or Call object, but 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 | Indicates that an unsupported attachment type was encountered. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Possibly an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Tried to access a closed stream. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Data Handler has no content. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Possibly an internal error. |
Action | Make sure your engine configuration is correct. |
Explanation | Child elements were not anticipated in the soap message. The soap message cannot be deserialized. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Your WSDL may be bad. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Probably an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The type mapping cannot be modified after registration has occurred. |
Action | Please correct your code. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Invalid TypeMapping registration. |
Action | Please correct your code. |
Explanation | Cannot change default type mapping after registration. |
Action | Please correct your code. |
Explanation | You cannot call this getPort method because there is no stub implementation of the interface. |
Action | Please change your code. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This may be a symptom of a Web service deployment problem or an incorrect SOAP request message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Exception. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Make sure that the JavaBean has a default constructor. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad argument was specified for -soapAction. |
Action | Use the correct Java2WSDL -soapAction option. |
Explanation | Suspect a problem with the Web service deployment, with the soap message, or hot swapping of the service's SoapBindingImpl class. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Informational message indicating which java classes are generated by WSDL2Java. |
Action | no action required. |
Explanation | The -style option of Java2WSDL is incorrect. |
Action | Use a correct -style option. |
Explanation | Suspect a Web service deployment error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Suspect a Web service deployment error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Only one class file may be specified for Java2WSDL. |
Action | Correct your invocation of Java2WSDL. |
Explanation | A class file must be specified for Java2WSDL. |
Action | Correct your invocation of Java2WSDL. |
Explanation | The WSDL file can only be specified once for WSDL2Java. |
Action | Correct your invocation of WSDL2Java. |
Explanation | The WSDL URI must be specified for WSDL2Java. |
Action | Correct your invocation of WSDL2Java. |
Explanation | Inappropriate value for the enumeration. |
Action | Please correct your code. |
Explanation | Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed. |
Action | All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service. |
Explanation | Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed. |
Action | All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service. |
Explanation | Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed. |
Action | All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service. |
Explanation | WSDL2Java does not support this XML Schema type. |
Action | Correct your wsdl. |
Explanation | Each message part must have an element or type attribute which locates the schema element/type. |
Action | Correct your wsdl. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Suspect a problem with deploying this Web service. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Suspect a problem with deploying this Web service. Probably an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The NormalizedString object could not be set due to an invalid value. |
Action | Correct the normalizedString value. |
Explanation | The Token object could not be set due to an invalid value. |
Action | Correct the token value. |
Explanation | Internal Error. |
Action | Make sure the indicate class complies with JAX-RPC. |
Explanation | Could not write the schema for the indicated class. This is probably due to an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | You probably specified an invalid class to Java2WSDL. |
Action | Correct the indicated class. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed. |
Action | All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service. |
Explanation | WSDL2Java error. |
Action | Please correct your wsdl. |
Explanation | WSDL2Java informational message. |
Action | No action required. |
Explanation | Error occurred while constructing a YearMonth object. |
Action | Use a correct value. |
Explanation | Error occurred while constructing a Year object. |
Action | Use a correct value. |
Explanation | Error occurred while constructing a Month object. |
Action | Use a correct value. |
Explanation | Error occurred while constructing a Day object. |
Action | Use a correct value. |
Explanation | Error occurred while constructing a MonthDay object. |
Action | Use a correct value. |
Explanation | Error occurred while constructing a Duration object. |
Action | Use a correct value. |
Explanation | This serializer cannot be used to serialize attributes. |
Action | Please correct your deployed type mappings. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to use the SourceDataHandlerSerializer to serialize a non-SourceStream object. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. This error usually indicates that information was missing in the PortDesc/WSDDPort in regards to the definition of the Web service operations. The engine attempts to deduce the missing information, which may result in this particular error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Correct your factory implementation. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | Invoke method failed. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | Missing factory implementation. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Cannot load the indicated factory. |
Action | Make sure that the factory can be loaded. |
Explanation | WSDD Deployment information is missing. This may be due to an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | WSDD Deployment information is missing. This may be due to an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | WSDL2Java error indicating that an element is referenced but no definition was found. |
Action | Please correct your wsdl. |
Explanation | A type or ref attribute is used to reference a type or element. |
Action | Please correct your wsdl. |
Explanation | This may be due to a deployment problems. |
Action | Make sure that the indicated class can be found and loaded. |
Explanation | Normally this indicates a problem with the missing or incorrect deployment information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. This is an unsupported api. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. This is an unsupported api. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An invalid binding operation was encountered in the wsdl. |
Action | Please correct the wsdl. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The SOAP request message received by the service does not match the WSDL definition. |
Action | Make sure that the SOAP message sent to the service matches the WSDL definition. |
Explanation | The binding fault must have a corresponding portType fault. |
Action | Please correct the wsdl |
Explanation | The binding fault must have a name. |
Action | Please correct the wsdl. |
Explanation | The binding fault must have an appropriate <soap:fault> element. |
Action | Please correct the wsdl. |
Explanation | The soap message is incorrect. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The response soap message is incorrect. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The -use option of Java2WSDL is incorrect. |
Action | Correct the -use option. |
Explanation | The -extraClasses option of Java2WSDL is incorrect. |
Action | Correct the -extraClasses option. |
Explanation | A method was encountered that has a return type, but Java2WSDL was invoked in a mode that assumes that the method is one way. |
Action | Correct the class. |
Explanation | Probably an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Probably an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This can be caused by an internal error or a bad input soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Cannot add a child SOAPElement to the indicated object. |
Action | Correct your code. |
Explanation | Cannot add the indicated child element. |
Action | Correct your code. |
Explanation | Cannot add a Text node to the indicated object. |
Action | Correct your code. |
Explanation | Cannot call setAttributes after the SOAPElement has attributes. |
Action | Correct your code. |
Explanation | Cannot call setMappingScope after the SOAPElement has a MappingScope. |
Action | Correct your code. |
Explanation | This is an unrecognized alternate content type. |
Action | Correct your code. |
Explanation | Expecting only one child element of the given qname. |
Action | Correct your 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 uri. |
Action | Correct your code or soap message. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The soap message has an illegal xmlns prefix. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Admin tool failed. |
Action | The Admin tool is not fully supported. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An exception was thrown during handler fault processing. |
Action | Inspect your handlers. |
Explanation | The indicated class could not be found and/or loaded. |
Action | Determine why the class was not found or loaded. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Warning. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | Warning. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Tried to illegally manipulate xml. |
Action | Correct your handler. |
Explanation | Cannot call this method in a managed container. |
Action | Correct your handler. |
Explanation | Cannot call this method in a managed container. |
Action | Correct your handler. |
Explanation | Deployment error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Probably an internal problem. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Informational Message. |
Action | No action required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The protocol for a JMS URL string should be "jms:" |
Action | Make sure that a proper JMS-style 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 | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 JMS correlation id in the reply message did not match the JMS message id in the request message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The JMS reply message should be of type javax.jms.BytesMessage, but it was a different type. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | To allow overloaded operations would cause duplicate xsi types of the same name. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Runtime set a response message onto the MessageContext for a one-way message. |
Action | Correct JAXRPC Handler logic. |
Explanation | An exception was thrown during handler fault processing. |
Action | Inspect your handlers. |
Explanation | It's not allowed to set a value the node as described in the exception. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 your wsdl. |
Explanation | The specified interface must subclass 'javax.xml.rpc.Service'. |
Action | Specify an interface that subclasses 'javax.xml.rpc.Service'. |
Explanation | The object can not 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | xsd:list itemTypes must be atomic values. |
Action | Correct the WSDL. |
Explanation | informational message. |
Action | no action required. |
Explanation | informational message. |
Action | no action required. |
Explanation | Runtime does not receive any HTTP Basic Authentication information from the prompt. Or the loginSource property is not configured. |
Action | Make sure userid and password are both entered at the prompt. Or read the InfoCenter to configure the loginSource property. |
Explanation | This is notification that a previous versioned DD file was found where the DD is to be written. And that a new version will be written. |
Action | If this is unexpected, check your DD versions. |
Explanation | This is notification that a previous versioned DD file was found where the DD is to be written. And that a new version will be written. |
Action | If this is unexpected, check your DD versions. |
Explanation | Expected valid CharacterEncoding for incoming message. |
Action | Correct CharacterEncoding for incoming message. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Examine exception stack trace for more detail. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An invalid empty string date/time value was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An invalid empty string time value was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An invalid empty string date value was found in a soap message. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified service locator must subclass the service interface. |
Action | Specify a service locator that subclasses the service interface. |
Explanation | The contents of the SOAP body should have been decrypted by web services security. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The mapping file is used to describe the java mappings for xml qnames. In this case, the qname is incorrect or not found. The corresponding information in the mapping file is ignored. |
Action | If this mapping file was created by non-IBM tooling, please contact contact the vendor. If 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 | Call.getOutputParams and Call.getOutputValues cannot be called unless there is output. There is no output until a call to invoke returns. On a call to invokeOneWay, there is never output. |
Action | Call Call.invoke before calling Call.getOutputParams or Call.getOutputValues. |
Explanation | Improper use of JAX-RPC API in handler. |
Action | Review and correct use of JAX-RPC APIs. |
Explanation | Improper use of JAX-RPC API in handler. |
Action | Review and correct use of JAX-RPC APIs. |
Explanation | Improper use of JAX-RPC API in handler. |
Action | Review and correct use of 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 | Could not get a secure socket factory using the SSL settings of JSSE |
Action | Verify your JSSE SSL setting if you intend to use JSSE SSL setting for the SSL configuration. |
Explanation | Configured HTTP proxy information. |
Action | None. |
Explanation | Configured HTTPS proxy information. |
Action | None. |
Explanation | Specified SSL configuration. It can be by a java property file, a SSL configuration alias, or the JSSE SSL settings. |
Action | None. |
Explanation | HTTP response from Proxy for the HTTP CONNECT request |
Action | None. |
Explanation | Attempt has been made to generate the code without first parsing the WSDL file. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | WSDL2Java issues this message if a file write attempt was denied by underlying file operating system. Most likely due to WSAD restrictions. |
Action | None. |
Explanation | WS-I mandates that the 'style/use' must be the same for 'input/outputs' and 'faults' in any one binding. For more details visit WS-I at: http://www.ws-i.org/ |
Action | Modify your WSDL document to make the 'style/use' settings for 'inputs, outputs' and/or 'faults' consistent. |
Explanation | The -javaSearch option of WSDL2Java is wrong. |
Action | Correct the -javaSearch option setting. |
Explanation | Internal Error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The wsdl has a relative namespace, such as "/home", and no ancestor absolute namespaces to pre-catenate and make an absolute namespace, such as "http://www.ibm.com/home". |
Action | Fix the namespaces in the wsdl. |
Explanation | Validation Error. An existing SEI class return type is not compatible with it's WSDL definition. |
Action | Correct the incompatibility between your existing SEI and WSDL document. |
Explanation | Validation Error. An existing SEI class parameter type is not compatible with it's WSDL definition. |
Action | Correct the incompatibility between your existing SEI and WSDL document. |
Explanation | Validation Error. An existing Java class field type is not compatible with it's WSDL definition. |
Action | Correct the incompatibility between your existing Java class and WSDL document. |
Explanation | Validation Error. An existing Enumeration class is missing a required method. |
Action | Add the specified method to the Enumeration class. |
Explanation | Validation Error. An existing Enumeration class contains an invalid method. |
Action | Remove specified method from the Enumeration class. |
Explanation | Validation Error. An existing Bean class does not contain required default constructor. |
Action | Add a default constructor to specified Bean. |
Explanation | Validation Error. Specified Bean class does not extend an appropriate Java class. |
Action | Change the specified bean class to extend a compatible Java class. |
Explanation | Validation Error. Specified Bean does NOT have corresponding bean properties for it's data members. |
Action | Make the data member public, or add corresponding getters and setters. |
Explanation | Validation Error. Specified fault class is not a Java Exception class. |
Action | Make the specified fault class extend java.lang.Exception. |
Explanation | Validation Error. Specified Fault class does not implement a constructor with correct number of parameters. |
Action | Make sure Fault class implements a public constructor with required parameters. |
Explanation | Validation Error. Specified Fault class does NOT have corresponding bean properties for it's data members. |
Action | Make the data member public, or add corresponding getters and setters. |
Explanation | Validation Error. An existing Fault class parameter type is not compatible with it's WSDL definition. |
Action | Correct the incompatibility between your existing Fault class and WSDL document. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | An unsupported binding type was requested. |
Action | Ensure that only valid binding types are requested. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
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 | None. |
Action | None. |
Explanation | Required property needs to be specified. |
Action | Specify required property. |
Explanation | See previously reported errors. |
Action | Fix cause of previously reported errors. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | WSLD file could not be found where it was expected. |
Action | Fix the EAR. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Either this SOAPElement does not contain a text node, or the text node does not refer to an attachment. |
Action | Make sure this is a swaRef element by calling isSwaRef. |
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 the parameters to addSwaRefTextNode are consistent. |
Explanation | File specified by user was not found in the file system. |
Action | Make sure file exists and/or that it was spelled correctly. |
Explanation | Import ile specified by in wsdl was not found in the file system. |
Action | Make sure file exists and/or that it was spelled correctly. |
Explanation | document/encoded is an invalid combination of style/use. |
Action | Use a valid combination of style/use: rpc/encoded rpc/literal document/literal |
Explanation | document/encoded is an invalid combination of style/use. |
Action | Use a valid combination of style/use: rpc/encoded rpc/literal document/literal |
Explanation | Configured syncTimeout value in seconds. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Inform the HTTP response from the server. |
Action | None. |
Explanation | No HTTP status information is available to determine the HTTP response. |
Action | Make sure the target HTTP server is up. |
Explanation | Received HTTP response indicates a new location for the target resource. |
Action | User may want to check WebSphere InfoCenter for details about how to accept the automatic redirection to the new location. |
Explanation | None. |
Action | None. |
Explanation | There are failures from the Channel Framework service. |
Action | Check errors reported by Channel Framework service in the log. |
Explanation | Found unsupported schema for using HTTP transport. |
Action | Verify the target endpoint address. |
Explanation | None. |
Action | None. |
Explanation | Runtime failed to get the HTTP proxy information to process the proxy connection. |
Action | Make sure the HTTP or HTTPS proxy information is configured properly. User may want to check WebSphere InfoCenter about how to configure for HTTP proxy. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
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 | None. |
Explanation | None. |
Action | None. |
Explanation | Sending current SOAP over HTTP request in indicated HTTP version. |
Action | None. |
Explanation | Unsupported HTTP version is detected. This is an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Invalid HTTP response is received. This could be an internal error. |
Action | None. |
Explanation | There are failures with the HTTP Channel service. |
Action | Check errors reported by HTTP Channel service in the log. |
Explanation | There are failures with the SSL Channel service. |
Action | Check errors reported by SSL Channel service in the log. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Indicate how many keystore password properties have been identified. |
Action | None. |
Explanation | An attempt was made to serialize a message with too deep a nesting. This could be due to a linked list with too many nodes. This problem could also be due to an attempt to serialize a graph containing looped references. |
Action | Please correct the data being serialized. |
Explanation | Appending "/wsdl" to a service URL is a request to retrieve a WSDL document that contains SOAP ports for the HTTP or JMS transports. If there are no such ports, this error is displayed instead of the WSDL document. |
Action | Modify the query to obtain the extended wsdl 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 | It's expected that every custom type mapping has a non-default namespace. |
Action | Correct the CustomBindingProvider.xml file. |
Explanation | None |
Action | None |
Explanation | Validation Error. Specified Bean class does not extend same extension base specified in WSDL document. |
Action | Change the specified Bean class or WSDL document to extend appropriate Java class. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Runtime found an unknown outbound connection object. It could be an internal error. |
Action | Check for connection exception in the log. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Access to a closed connection is attempted. This could be an internal error. |
Action | Check for connection exception in the log. |
Explanation | An exception has caused the release of saved virtual connection object and outbound service context. |
Action | Check from the log for the previous exception caught. |
Explanation | None. |
Action | None. |
Explanation | WSDL2Java error indicating that an attribute is referenced but no definition was found. |
Action | Please correct your wsdl. |
Explanation | Based on a Java system property setting, each HTTP connection will be retried until the connection succeeds. However, this is not recommended as deadlock may happen. |
Action | User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections. |
Explanation | Based on a Java system property setting, each HTTP connection will be retried for the configured number of times. However, user needs to be cautious about changing this property as deadlock may sometimes happen. Default value is 3. |
Action | User should consider to modify the configuration of the target's 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 | User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | Internal discovery problem, perhaps with classloader. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Internal discovery problem, perhaps with classloader. Can't continue. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad property detected on the MessageContext or OperationDesc. This could be caused by an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A bad property detected on the MessageContext or OperationDesc. This could be caused by an internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Either the above custom binder does not exist or it is not in the classpath for the context classloader. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The -MIMEstyle option of Java2WSDL is incorrect. |
Action | Use a correct -MIMEstyle option. |
Explanation | WSDL2Java error indicating that a group is referenced but no definition was found. |
Action | Please correct your wsdl. |
Explanation | WSDL2Java error indicating that a attributeGroup is referenced but no definition was found. |
Action | Please correct your wsdl. |
Explanation | There will be no compression performed for the HTTP content encoding in the HTTP request or the HTTP response. Hence, the Web services property for HTTP compression has been ignored. |
Action | User can consider the followings: 1.) validate the value of Web services property for HTTP compression, 2.) check for error messages from HTTP Channel, or 3.) do nothing if compression is not needed. |
Explanation | Indicate whether the described compression type are enabled. Note that gzip and x-gzip use the same compression mechanism. |
Action | Check the Web services property for HTTP compression is configured as needed. |
Explanation | Indicate whether the compression type of deflate is enabled. |
Action | Check the Web services property for HTTP compression is configured as needed. |
Explanation | Indicate what type of HTTP Channel is used for HTTP connection. It could be an In-process or network type. |
Action | None. |
Explanation | There might be an error when the system attempted to find an Inprocess HTTP Channel. However, this may not be a problem unless an in-process connection is required. The system will proceed with a network type of Channel instead. |
Action | If necessary, check the trace for Work Load Management(WLM) or Dynamic Work Load Management Client(DWLMclient) errors. |
Explanation | The printed data was used to map to a valid cluster name. |
Action | None. |
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 indicates the value set by the web services client for acceptable content-codings in the HTTP response. Please refer to the specification of Hypertext Transfer Protocol for further details. Header value of null indicates empty Accept-Encoding header in the incoming HTTP request;hence, no content encoding is done in the HTTP response. |
Action | If it is a WebSphere Web services client, check the Web services property for Http compression encoding of the target service port. Make sure the value is configured properly. |
Explanation | This printed data was used to map for a channelframework endpoint object that can be used later to create In-process connection. |
Action | None. |
Explanation | The specified endpoint was used to invoke Service.getPort. |
Action | Correct the invocation of Service.getPort. |
Explanation | The specified port was used to invoke Service.createCall. |
Action | Correct the invocation of Service.createCall. |
Explanation | The specified operation was used to invoke Service.createCall. |
Action | Correct the invocation of Service.createCall. |
Explanation | Validation Error. Specified Bean does not correctly define a bean property for the designated data member. |
Action | Make the data member public, or add an appropriate setter method. Be particularly careful to ensure that the get and set methods use the same capitalization. |
Explanation | The following message was received as a Web services request. |
Action | None. |
Explanation | The following message was received in response to a previous Web services request. |
Action | None. |
Explanation | The following message was sent as a Web services request. |
Action | None. |
Explanation | The following message was sent as a response to a Web services request. |
Action | None. |
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. More details in messages to follow. Code/Artifacts generation has been suspended. |
Action | Correct problems reported and try again. |
Explanation | Attempted to protect the SOAP message body befor invoking the JAX-RPC handlers, however, an unknown error occurred while doing so. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The JSR109 mapping file defined a name for the xml construct that is different than the default mapping. |
Action | none |
Explanation | The custom binder defined a name for the xml construct that is different than the default mapping. |
Action | none |
Explanation | Java reflection indicates that the name of the xml construct that is different than the default mapping. |
Action | none |
Explanation | Performing introspection of indicated SEI. |
Action | none |
Explanation | Performing introspection of indicated class. |
Action | none |
Explanation | An invalid portType operation was encountered in the wsdl. |
Action | Please correct the wsdl. |
Explanation | When property is specified, the corresponding property must also be specified. |
Action | Respecify the property using bindningTypes http. |
Explanation | When property is specified, the corresponding property must also be specified. |
Action | Respecify the property using bindningTypes jms. |
Explanation | When propertie is specified, the corresponding property must also be specified. |
Action | Respecify the property using bindingTypes ejb. |
Explanation | Inconsistent portType and binding operation were encountered in the wsdl. |
Action | Make sure wsdl is correct. |
Explanation | none. |
Action | none |
Explanation | The indicated Identity object has been received from WS-Addressing. If null, transport will attempt to map one by the RequestMapper. |
Action | If clustering is used, check for errors from WS-Addressing in the trace. |
Explanation | The indicated Identity object cannot be mapped to a valid endpoint. |
Action | If null, check for errors from Clustering and ChannelFramework in the trace. |
Explanation | An exception was caught. However, the exception can be benign since transport can proceed to next option using the RequestMapper to resolve the endpoint. |
Action | If applicable, check for errors related to WS-Addressing. |
Explanation | An exception was caught. However, the exception can be benign since transport can proceed to next option using the default channels to resolve the endpoint. |
Action | If applicable, check for errors related to Dynamic Work Load Management Client. |
Explanation | The service endpoint implementation has thrown an exception. This may or may not 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 may be a symptom of an incorrect wsdl. |
Action | Fix your wsdl to remove ambiguity, or CMSG002 |
Explanation | 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 your wsdl to remove ambiguity. |
Explanation | 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 |
Explanation | This informational message describes the current condition of the outbound HTTP connection pool. |
Action | No user 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 | None. |
Action | No user action is required. |
Explanation | None. |
Action | No user 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 exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | None. |
Action | No user 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 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 WSDL message part name and the element attributes to ensure unique parameters. |
Explanation | The input SEI references a class nested inside another class. This is unsupported. |
Action | Change the Java structure. |
Explanation | Found a non WSDL or schema document being referenced through a wsdl:import. |
Action | Make sure the document being imported is a valid WSDL document. WSDL:importsimporting a schema is allowed but not recommended. |
Explanation | Found that a wsdl:import is being used to import a schema document instead of a WSDL file. |
Action | To be WS-I compliant you must make sure wsdl:imports only import WSDL documents, and that xsd:imports are used instead to import schemas. |
Explanation | Found that a wsdl:import namespace attribute contains a relative URI. This is not WS-I compliant. |
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 is not WS-I compliant. |
Action | To be WS-I compliant you must make sure the schemaLocation attribute resolves to a documet whose root element is a schema. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A connection to the remote host was not possible. |
Action | Check connection and/or errors reported for more details. |
Explanation | A Schema import, include or redefine is not being defined within an xsd:schema element. This is not WS-I compliant. |
Action | To be WS-I compliant make sure schemas are being imported/included/redefined from within schema elements. Use WSDL "imports" from within a WSDL definition document. |
Explanation | A wsdl:import statement is missing the 'location' attribute. Processing can not go on. |
Action | Add the 'location' attribute to the specified wsdl:import element. |
Explanation | The specified WSDL document is not WS-I compliant as it does not preserve element order specified by WS-I. WS-I specifies that wsdl:import elements MUST precede all other elements from the WSDL namespace except wsdl:documentation. |
Action | To be WS-I compliant change the order of the wsdl elements defined, and make sure wsdl:imports are only preceded by wsdl:documentation, wsdl:#comment and/or wsdl:#text. |
Explanation | The specified WSDL document is not WS-I compliant as it does not preserve element order specified by WS-I. WS-I specifies that wsdl:types elements MUST precede all other elements from the WSDL namespace except wsdl:documentation and wsdl:import. |
Action | To be WS-I compliant change the order of the wsdl elements defined, and make sure wsdl:types are only preceded by wsdl:documentation, wsdl:#comment, wsdl:#text and/or wsdl:import. |
Explanation | The 'namespace' attribute of the wsdl or xsd import has not been defined and the file being imported does not contain a 'targetNamespace'. This is not a supported configuration. |
Action | Make sure both, the 'namespace' attribute and the 'targetNamespace' of the imported file, are defined and equal in value. |
Explanation | WS-I requires import namespace attributes to equal the value of the imported document's targetNamespace. |
Action | Make sure both, the 'namespace' attribute and the 'targetNamespace' of the imported file, are defined and equal in value. |
Explanation | None. |
Action | No user action is required. |
Explanation | informational message. |
Action | no action required. |
Explanation | informational message. |
Action | no action 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This operation is not supported by SAAJ 1.2. |
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 source of exception using the class name of the dispatcher and the call stack presented in the message. If it is from an external provider, contact the provider for 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 | WSDL2Java does not support 'redefine' elements with 'extension's. |
Action | Correct your wsdl or schema. Completely define the type within the 'redefine'. |
Explanation | None. |
Action | None. |
Explanation | Runtime has found SSL properties programmatically set on the current thread. The same properties are registered with the event listener. SSL properties programmatically set always have the highest precedence. |
Action | If this is not intended, application should not programmatically set the properties prior to invocation. |
Explanation | Based on the JAX-RPC model, the SSL configuration alias or SSL certificate alias can be specified and may have been found from the message's context. The information is used for the SSL connection of the current invocation. However, there may not be value for each alias if the alias has never been specified. |
Action | If this is not intended, application should not set the properties prior to invocation. Read InfoCenter for further information. |
Explanation | WebSphere SSL runtime failed to resolve for an effective SSL configuration. Attempt to default to the JSSE system properties. |
Action | Make sure SSL configuration is properly set for this invocation following the precedence rules specified in the WebSphere InfoCenter. |
Explanation | 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 WebSphere InfoCenter. |
Explanation | Received SSL properties from the WebSphere security. The same properties are registered with the event listener. |
Action | None. |
Explanation | Internal operation. |
Action | None. |
Explanation | Internal operation. The connection object marked is not usable. |
Action | None. |
Explanation | Internal operation. The connection object invalidated is not usable. |
Action | None. |
Explanation | Internal operation. |
Action | None. |
Explanation | This exception may be due to a timing problem caused by the asynchronous operation done by the Unified Clustering Framework. The web services engine will attempt to query from the UCF again. |
Action | None. |
Explanation | The second query fails, the engine proceed to next option using default channels. |
Action | If Unified Clustering is needed, this is an error. Please check the trace for any error from the clustering. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | The application uses a type that is not a JAX-RPC supported type. Although we proceed 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 | New WS-Addressing destination EPR is being set. However, the service name from the EPR does not match the original service name configured in this object. |
Action | Enable WS-Addressing trace and check for WS-Addressing errors. |
Explanation | Standard IBM Copyright. |
Action | No user action is required. |
Explanation | Standard IBM banner displayed by the web services emitter. |
Action | No user action is required. |
Explanation | Standard IBM banner displayed by the Java to WSDL emitter. |
Action | No user action is required. |
Explanation | Standard IBM banner displayed by the WSDL to Java emitter. |
Action | No user action is required. |
Explanation | Invalid HTTP host value. This could be an internal error. |
Action | None. |
Explanation | Invalid HTTP port value. This could be an internal error. |
Action | Modify or add valid port to the endpoint URL. |
Explanation | Provide information about local and mapped cell names. The mapped cell name can be from a remote cluster. |
Action | No user action is required. |
Explanation | Unable to evaluate the current EPR in the WS-Addressing runtime. |
Action | Make sure the EPR is set properly. Enable WS-Addressing trace for details. |
Explanation | Uses sendSOAPRequestAsync() to make a re-directed asynchronous delivery. This happens only with re-directed asynchronous delivery due to WS-Addressing. |
Action | No user action is required. |
Explanation | Informational. |
Action | No user action is required. |
Explanation | Informational. Look for this message to track the response received for the previous asynchronous delivery caused by WS-Addressing. |
Action | No user action is required. |
Explanation | Look for this message to check error in the previous asynchronous delivery caused by WS-Addressing. |
Action | Check for the exception logged after this message. |
Explanation | New WS-Addressing destination EPR is being set. However, the port name from the EPR does not match the original port name configured in this object. |
Action | Enable WS-Addressing trace and check for WS-Addressing errors. |
Explanation | WSDL2Java does not currently support XML schema substitution groups. Any reference to a substitution group is ignored. |
Action | Modify your WSDL or do not expect substitution group designations in generated artifacts. |
Explanation | Java2WSDL only uses qualified or unqualified for the elementFormDefault option. |
Action | Modify your Java2WSDL invocation to include a valid argument for the elementFormDefault option. |
Explanation | Java2WSDL 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 | WSDL2Java encountered unsupported binding namespace {0} and will continue code generation process for the supported binding(s). |
Action | To remove this warning, remove the unsupported binding namespace from your WSDL. |
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 | The indicated method requires SAAJ 1.3 support. This support is not available in the the installed version of WebSphere. |
Action | Use an SAAJ 1.2 method or upgrade to a new version of WebSphere. |
Explanation | The indicated method requires DOM Level 3, which is part of the SAAJ 1.3 support. This method is not available in the installed version of WebSphere. |
Action | Use a DOM Level 2 method or upgrade to a new version of WebSphere. |
Explanation | The request information is not available when the SOAPConstants.DYNAMIC_SOAP_PROTOCOL is used. |
Action | Create the SOAP messaage with a SOAP 1.1 or SOAP 1.2 protocol. |
Explanation | The indicated method is only valid for the SOAP 1.2 Protocol. This requirement is defined by the SAAJ 1.3 specification. |
Action | Use method that is valid for your SOAP Protocol. |
Explanation | The indicated protocol requires SAAJ 1.3 support. This support is not available in the the installed version of WebSphere. |
Action | Use the SOAP 1.1 protocol or upgrade to a new version of WebSphere. |
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 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 | SAAJ 1.3 requires that the prefix be bound. This means that a namespace declaration must exist in an ancestor element. |
Action | Correct the code that called addChildElement. |
Explanation | The SOAPEnvelope and SOAPMessage must have the same protocol. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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. |