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