WebSphere NOT SPECIFIED     Operating Systems: All supported

WSWS3000I: WSDL2Java emitter Usage: WSDL2Java [options] WSDL-URI Important Options: -r, -role {argument} the J2EE role that identifies which files to generate. Valid arguments are: "develop-client" : (default) generates files for client development "develop-server" : generates files for server development "deploy-client" : generates binding files for client deployment "deploy-server" : generates binding files for server deployment "client" : combination of "develop-client" and "deploy-client" "server" : combination of "develop-server" and "deploy-server" -c, -container {argument} indicates the J2EE container. Valid arguments are: "none" : indicates no container "client" : indicates client container "ejb" : indicates EJB container "web" : indicates Web container If client role the default argument is "none". If server role the container must be either "ejb" or "web". The same container option must be used for both development and deployment. -o, -output {argument} output directory for emitted files. -m, -inputMappingFile {mapping-file} the location of the Java to WSDL mapping. -i, -introspect introspect existing classes to determine mapping details. -C, -classpath {paths} classpath to use for class introspection. Other Options: -h, -help print this message and exit. -X, -helpX print extended options. -v, -verbose print verbose informational messages. -N, -NStoPkg {namespace}={package} mapping of namespace to package. Alternatively declare this information in the mapping file. -O, -timeout {argument} number of seconds to wait for accessing WSDL-URI. (default is 45 seconds), specify -timeout -1 to disable. -g, -genResolver generate an absolute-import resolver. -u, -useResolver specify an absolute-import resolver to use during parsing. -d, -deployScope {argument} indicates how to deploy the server. Valid arguments are: "Request", "Session", "Application".
Problem These are the options to WSDL2Java.
User response Use the specified options when invoking WSDL2Java.
WSWS3001I: Info: Extended Options: -U, -user {argument} login username to access the WSDL-URI. -P, -password {argument} login password to access the WSDL-URI. -a, -all generate java files for all types, even unreferenced ones. -z, -noDataBinding map all types (including base schema types) to SOAPElement. -t, -testCase emit template junit testcase class for testing Web service. -D, -Debug print debug information. -f, -fileNStoPkg {argument} file of NStoPkg mappings (default NStoPkg.properties). -j, -genJava {argument} generate Java files. Valid arguments are: "No" "IfNotExists" (default) "Overwrite" -s, -javaSearch {argument} when -genJava is set to "IfNotExists", determines how file existence is detected. Valid arguments are: "File" (default) "Classpath" "Both" -x, -genXML {argument} generate XML and XMI files. Valid arguments are: "No" "IfNotExists" (default) "Overwrite" -E, -genEquals {boolean} Enable the hashcode/equal generation. Valid arguments are: "yes" "no" (default) -I, -genImplSer {boolean} Have generated beans implement java.io.Serializable. Valid arguments are: "yes" "no" (default) -y, -noWrappedArrays Disable .NET wrapped array pattern. Generate beans containing arrays. -w, -noWrappedOperations Disable .NET wrapped operation pattern. Generate request and response beans.
Problem These are the extended options to WSDL2Java.
User response These are advanced options that users should not generally use.
WSWS3002I: Java2WSDL emitter Usage: Java2WSDL [options] class-of-portType Options: -location {argument} web service location url -output {wsdl} output WSDL file name -input {argument} input wsdl file name used to build wsdl from existing wsdl information -bindingTypes {argument} list of binding types to include in the wsdl file the default is "http" examples: -bindingTypes http,ejb -bindingTypes http,jms -style {argument} valid arguments: document (the default): generate document style wsdl rpc: generate rpc style wsdl -use {argument} valid arguments: literal (the default): literal use encoded: encoded use -transport {argument} This option has been deprecated. Use the -bindingTypes option instead. -portTypeName {portType} name of the portType defaults to name of the input class -bindingName {binding} name of the binding defaulted from portType if not specified -serviceElementName {service} name of the service defaulted from portType name if not specified -servicePortName {port} name of the port defaulted from -location if not specified -namespace {argument} target namespace of wsdl -PkgtoNS {package}={namespace} mapping of package names to namespaces -implClass {class-name} class that contains implementation of methods in class-of-portType. The debug information in the class is used to obtain the method parameter names, which are used to set the WSDL part names. -extraClasses {classes} other classes that should be added to the wsdl -classpath {paths} classpath to use for class introspection. -verbose display verbose messages -help displays this message -helpX displays extended options
Problem These are the options to Java2WSDL.
User response Use the specified options when invoking Java2WSDL.
WSWS3003I: Info: Extended Options: -wrapped {boolean} indicate if wsdl should respect "wrapped" rules valid only for -style document and -use literal. the default is true. -stopClasses {argument} space or comma separated list of class names which will stop inheritance search when processing classes -methods {argument} space or comma separated list of method names from the SEI which are to be exposed in the output wsdl -soapAction {argument} valid arguments: OPERATION sets soapAction field to the operation name. NONE sets soapAction field to "". DEFAULT uses deployment information to set the field. -outputImpl <file> specify if you want both interface and implementation wsdls -locationImport {argument} location of interface WSDL file -namespaceImpl {argument} target namespace for implementation WSDL -MIMEStyle (argument} valid arguments: AXIS: AXIS style MIME representation WSDL11 (default): WSDL 1.1 MIME representation swaRef: WS-I BP 1.1 representation (swaRef where appropriate) -propertiesFile {argument} filename of a properties file that contains a list of class names which should be added to the type section of the output wsdl. Example of file content: extraClasses=com.ibm.Class1,com.sun.Class2,org.apache.Class3 -voidReturn {argument} valid arguments: ONEWAY:treat methods with void returns as one-way TWOWAY:treat methods with void returns as two-way -debug display debug messages -properties <property settings> sets binding-specific properties to be used by binding generators example: -properties prop1=value1,prop2=value2 Supported binding-specific properties:
Problem These are the extended options to Java2WSDL.
User response These are advanced options that users should not generally use.
WSWS3004W: Warning: The -location was not set, the value "{0}" is used instead.
Problem The -location option is a required option.
User response Please specify the -location option.
WSWS3005W: Warning: The -server-side option must have an argument that is Bean or EJB. Defaulting to Bean.
Problem The -server-side option is incorrect.
User response Please specify the correct -server-side option.
WSWS3006W: Warning: The argument of the -transport option must be "jms" or "http". The default setting ("http") will be used.
Problem The -transport option is incorrect.
User response Please specify the correct option.
WSWS3007E: Error: The {0} operation of {1} has an output element. This output element is removed and the operation is changed to one-way.
Problem This pre-existing operation has an output element. It is removed.
User response None.
WSWS3008E: Error: The {0} operation of {1} has a fault element. The faults are removed and the operation is changed to one-way.
Problem This pre-existing operation has a fault element. It is removed.
User response None.
WSWS3009I: Info: Loading Class {0}
Problem Loading specified class.
User response None.
WSWS3010I: Info: Generating {0} {1}
Problem Generating indicated construct.
User response None.
WSWS3011E: Invalid destination type "{0}" specified within a JMS endpoint URL.
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.
WSWS3012E: Invalid property "{0}" encountered in JMS endpoint URL.
Problem A JMS endpoint URL string contained an unrecognized property.
User response Correct the JMS endpoint URL and re-try.
WSWS3013E: The JMS endpoint URL is missing one or more of the following required properties: connectionFactory, destination, targetService
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.
WSWS3014E: Error creating InitialContext: {0}
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.
WSWS3015E: Caught NamingException: {0}
Problem The specified error occurred during a JNDI 'lookup' operation.
User response Ensure that the JNDI name is correct.
WSWS3016E: Caught JMSException: {0}
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.
WSWS3017E: Linked Exception: {0}
Problem None.
User response None.
WSWS3018E: Caught exception during request processing: {0}
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.
WSWS3019E: Caught WebServicesFault: {0}
Problem The specified WebServicesFault exception occurred.
User response Use the detailed information in the original error message to determine how to correct the problem.
WSWS3020E: Error getting server engine.
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/.
WSWS3021E: The required "{0}" property was not present in the inbound JMS request message.
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/.
WSWS3022E: Unrecognized inbound JMS request message type.
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.
WSWS3023E: Two-way requests are not supported for topic destinations.
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.
WSWS3024E: Root part containing SOAP envelope not found. contentId = {0}
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/.
WSWS3025E: Error: Could not locate a parameter named {0} for {1}.
Problem Suspect a bad mapping file supplied to WSDL2Java.
User response Correct your mapping file.
WSWS3026E: Error: The argument of the -voidReturn option must be "oneway" or "twoway".
Problem The -voidReturn option is incorrect.
User response Please specify the correct option.
WSWS3027E: Error: The {0} SAX event is not supported by SOAP.
Problem The message is not a legal SOAP message.
User response Contact party that sent this message.
WSWS3028E: Error: A _Helper class was not found for {0}.
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.
WSWS3029W: Warning: The xml construct named {0} cannot be mapped to a java type. The construct will be mapped to javax.xml.soap.SOAPElement.
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.
WSWS3030E: Error: An internal error occurred while trying to locate the target method. Debug:{0}
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/.
WSWS3031E: Error: Serialization cannot occur for {0}. There are no registered type mappings.
Problem The indicated object cannot be serialized.
User response Make sure that a proper serializer is registered.
WSWS3032I: Info: Attempt to get a secure socket factory using KeyStore: {0} and TrustStore: {1}, or Cryptographic token in: {2}
Problem Used either a KeyStore/TrustStore pair or a cryptographic token to get a secure socket factory
User response None.
WSWS3033E: Error: Deserialization cannot occur for {0}.
Problem The indicated type cannot be deserialized.
User response Make sure that a proper deserializer is registered.
WSWS3034E: Error: The OperationDesc for {0} was not matched to a method of {1}. Debug:{2}
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/.
WSWS3035E: Error: {0}.{1} threw RuntimeException.
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.
WSWS3036I: Replacing response message with SOAP Fault. Original Response Message: {0}
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.
WSWS3037E: Error: Serialization cannot occur for {0}.
Problem The indicated object cannot be serialized.
User response Make sure that a proper serializer is registered.
WSWS3038E: Error: Deserialization cannot occur for {0}. There are no registered type mappings.
Problem The indicated type cannot be deserialized.
User response Make sure that a proper deserializer is registered.
WSWS3039E: Error: Resource has been deleted.
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/.
WSWS3040E: Error: Malformed arrayType value ''{0}''
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/.
WSWS3041E: Error: Bad authentication type (I can only handle "Basic").
Problem Only Basic authentication is supported with the SimpleServerEngine.
User response You should not be using the SimpleServerEngine.
WSWS3042E: Error: Invalid boolean (found {0}).
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/.
WSWS3043E: Error: Unexpected characters in a calendar value: {0}
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/.
WSWS3044E: Error: Bad character or insufficient number of characters in hex string.
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/.
WSWS3045E: Error: Invalid date: {0}
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/.
WSWS3046E: Error: Invalid date/time: {0}
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/.
WSWS3047E: Error: Cannot deserialize element {1} of bean {0}.
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/.
WSWS3048E: Error: Class ''{0}'' cannot be specified as a Handler class.
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
WSWS3049E: Error: A bad Holder class was encountered: {0}
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/.
WSWS3050E: Error: Explicit array length is not a valid integer ''{0}''.
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/.
WSWS3051E: Error: No ''name'' attribute was specified in an undeployment element.
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/.
WSWS3052E: Error: Bad envelope namespace: {0}
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/.
WSWS3053E: Error: An attempt was made to construct a Name object with an invalid string: {0}
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/.
WSWS3054E: Error: An attempt was made to construct a NCName object with an invalid string: {0}
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/.
WSWS3055E: Error: An attempt was made to construct a NegativeInteger object with an invalid string: {0}
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/.
WSWS3056E: Error: An attempt was made to construct a NMToken object with an invalid string: {0}
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/.
WSWS3057E: Error: An attempt was made to construct a NonNegativeInteger object with an invalid string: {0}
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/.
WSWS3058E: Error: An attempt was made to construct a NonPositiveInteger object with an invalid string: {0}
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/.
WSWS3059E: Error: Malformed offset attribute ''{0}''.
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/.
WSWS3060E: Error: Invalid Parameter mode {0}.
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/.
WSWS3061E: Error: Malformed position attribute ''{0}''.
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/.
WSWS3062E: Error: portName should not be null.
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.
WSWS3063E: Error: An attempt was made to construct a PosInteger object with an invalid string: {0}
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/.
WSWS3064E: Error: Cannot handle non-GET, non-POST request.
Problem SimpleServerEngine does not understand the request.
User response Don't use the SimpleServerEngine.
WSWS3065E: Error: Unrecognized -scope: {0}. Ignoring it.
Problem The argument of the scope option must be Request, Application, or Session.
User response Use the proper -scope option when invoking WSDL2Java.
WSWS3066E: Error: Expected ''envelope'' but found {0}
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/.
WSWS3067E: Error: Invalid time: {0}
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/.
WSWS3068E: Error: Invalid timezone: {0}
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/.
WSWS3069E: Error: Found languageSpecificType namespace ''{0}'', expected ''{1}''
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/.
WSWS3070E: Error: An attempt was made to construct an UnsignedByte object with an invalid string: {0}
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/.
WSWS3071E: Error: An attempt was made to construct an UnsignedShort object with an invalid string: {0}
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/.
WSWS3072E: Error: An attempt was made to construct an UnsignedInt object with an invalid string: {0}
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/.
WSWS3073E: Error: An attempt was made to construct an UnsignedLong object with an invalid string: {0}
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/.
WSWS3074E: Error: Cannot add a second body to a soap envelope.
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/.
WSWS3075E: Error: User ''{0}'' not authenticated (unknown user).
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/.
WSWS3076E: Error: User ''{0}'' not authenticated.
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/.
WSWS3077E: Error: User ''{0}'' not authorized to ''{1}''
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/.
WSWS3078E: Error: Cannot convert {0} to bytes.
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/.
WSWS3079E: Error: Cannot convert form {0} to String.
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/.
WSWS3080E: Error: Could not convert {0} to bean field ''{1}'', type {2}
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/.
WSWS3081E: Error: Could not convert value to int.
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/.
WSWS3082E: Error: Cannot serialize null arrays.
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/.
WSWS3083E: Error: getURL failed to correctly process URL; protocol not supported.
Problem Tool option error. See other messages.
User response Fix the URL.
WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize.
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/.
WSWS3085E: Error: Cannot invoke Call with null namespace URI for method {0}
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/.
WSWS3086E: Error: Cannot serialize a {0} with the ArraySerializer.
Problem The indicated class cannot be serialized with the array serializer.
User response Suspect a problem with the deployment information.
WSWS3087E: Error: Cannot serialize non-Elements with an ElementSerializer.
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/.
WSWS3088E: Error: Cannot serialize a raw object with the SimpleSerializer.
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.
WSWS3089E: Error: Cannot set location URI: {0}
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/.
WSWS3090E: Error: Unable to tunnel through {0}:{1}. Proxy returns "{2}"
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/.
WSWS3091E: Error: Changing admin password.
Problem Changed passwords on AdminClient.
User response AdminClient is not fully supported.
WSWS3092E: Error: SOAPElement.setAlternateContent called when a child element is present.
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/.
WSWS3093E: Error: Could not create Call object in AdminClient.
Problem Internal Error.
User response Don't use AdminClient.
WSWS3094E: Error: WSDDPort couldn't construct provider!
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/.
WSWS3095E: Error: Connection closed.
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/.
WSWS3096E: Error: Duplicate file name: {0}. Hint: you may have mapped two namespaces with elements of the same name to the same package name.
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.
WSWS3097E: Error: Emitter failure. All input parts must be listed in the parameterOrder attribute of {0}
Problem The parameter order attribute in the wsdl is incorrect.
User response Fix your wsdl.
WSWS3098E: Error: Emitter failure. Cannot find endpoint address in port {0} in service {1}
Problem The endpoint address cannot be found.
User response Fix your wsdl.
WSWS3099E: Error: Emitter failure. Invalid endpoint address in port {0} in service {1}: {2}
Problem The endpoint address is invalid.
User response Fix your wsdl.
WSWS3100E: Error: Emitter failure. No binding found for port {0}
Problem Specify a binding on the service wsdl port.
User response Fix your wsdl
WSWS3101E: Error: Emitter failure. No binding entry found for {0}
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/.
WSWS3102E: Error: Emitter failure. No portType entry found for {0}
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/.
WSWS3103E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document. Hint: make sure {port binding=".."} is fully qualified.
Problem The binding must be defined if referenced.
User response Fix the WSDL.
WSWS3104E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document {1}. Hint: make sure {port binding=".."} is fully qualified.
Problem The binding must be defined if referenced.
User response Fix the WSDL.
WSWS3105E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document. Hint: make sure {binding type=".."} is fully qualified.
Problem The portType must be defined if referenced.
User response Fix the WSDL.
WSWS3106E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document {1}. Hint: make sure {binding type=".."} is fully qualified.
Problem The portType must be defined if referenced.
User response Fix the WSDL.
WSWS3107E: Error: Generic Error.
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/.
WSWS3108E: Error: Error: {0}
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/.
WSWS3109E: Error: Error invoking Web service operation: {0}
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/.
WSWS3110E: Error: Error processing ''{0}''
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/.
WSWS3111E: Error: Error determining if {0} already exists. Will not generate this file.
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/.
WSWS3112E: Error: Generating WebServicesFault due to missing SOAPAction.
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/.
WSWS3113E: Error: Cannot add a second header to a soap envelope.
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/.
WSWS3114E: Error: Internal error.
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/.
WSWS3115E: Error: Configuration file directory ''{0}'' is not readable.
Problem The specified directory cannot be read.
User response Fix your configuration.
WSWS3116W: Warn: PERFORMANCE ALERT: The following message is re-parsed: {0}
Problem Non performant serialization encountered.
User response Examine code and make appropriate changes.
WSWS3117E: Error: Invalid container type (expected "ejb", "web", "client" or "none"), defaulting to "none".
Problem The -container option of WSDL2Java is wrong.
User response Fix the option setting.
WSWS3118E: Error: Invalid role (expected "develop-client", "deploy-client", "develop-server", or "deploy-server"), defaulting to "develop-client".
Problem The -role option of WSDL2Java is wrong.
User response Fix the option setting.
WSWS3119W: Warning: Invalid option combination: -role develop-server and -container client or -container none are invalid. The -container will be defaulted to "web".
Problem The Web service always runs in a web or ejb container.
User response Fix the options and rerun WSDL2Java.
WSWS3120E: Error: Configuration is missing.
Problem This is most likely due to a previous error with the Web services deployment descriptor.
User response Review the log for previous errors.
WSWS3121I: Info: {0} is a oneway operation.
Problem informational message.
User response no action required.
WSWS3122E: Error: Could not find service {0} referenced in URI {1}
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.
WSWS3123E: Error: Javaclass {0} specified for handler {1} must implement {2} OR {3}. The handler will be skipped.
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.
WSWS3124W: Warning: Invalid -genJava option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Problem The -genJava option of WSDL2Java is wrong.
User response Correct the option setting.
WSWS3125W: Warning: Invalid -genXML option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Problem The -genXML option of WSDL2Java is wrong.
User response Correct the option setting.
WSWS3126E: Error: Could not get a secure socket factory from the following SSL Configuration: {0}.
Problem Could not get a secure socket factory.
User response Correct your SSL configuration.
WSWS3127E: Error: Invalid WSDD element ''{0}'' (wanted ''{1}'').
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/.
WSWS3128E: Error: Could not make envelope from bytes.
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/.
WSWS3129E: Error: Only interfaces may be used for the proxy Class argument of the Service.getPort method.
Problem The getPort method requires a proxy interface.
User response Correct the invocation of the getPort method.
WSWS3130E: Error: Only interfaces which extend java.rmi.Remote may be used for the proxy Class argument of the Service.getPort method.
Problem The proxy Class argument must be an interface that extends java.rmi.Remote.
User response Fix the invocation of the getPort method.
WSWS3131E: Error: Must specify a password for AdminClient.
Problem A password must be supplied.
User response AdminClient is not fully supported.
WSWS3132E: Error: No target service was found.
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/.
WSWS3133E: Error: Need to specify a user for authorization.
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/.
WSWS3134E: Error: Remote administrator access is not allowed.
Problem Cannot administer remotely.
User response The Admin class is not fully supported.
WSWS3135E: Error: Body not found.
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/.
WSWS3136E: Error: No deserializer defined for array type {0}
Problem The array of the indicated component type could not be deserialized.
User response This problem may be due to invalid deployment information.
WSWS3137E: Error: No deserialization context to use in SOAPElement.convertToObject().
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/.
WSWS3138E: Error: No custom elements allowed at top level until after the <body> tag.
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/.
WSWS3139E: Error: No deserializer for {0}
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/.
WSWS3140E: Error: Deserializing parameter ''{0}'': could not find deserializer for type {1}
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/.
WSWS3141E: Error: Could not get DOM document: XML was "{0}"
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/.
WSWS3142E: Error: Could not find Web services engine.
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/.
WSWS3143W: Warning: Expected instance of ''EngineConfiguration'' in environment.
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/.
WSWS3144E: Error: Cannot locate handler: {0}
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/.
WSWS3145E: Error: No HandlerProvider ''handlerClass'' option was specified.
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/.
WSWS3146E: Error: No handlers in {0} ''{1}''
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/.
WSWS3147E: Error: no {0} header!
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/.
WSWS3148E: Error: Processing instructions are not allowed within SOAP messages.
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/.
WSWS3149E: Error: {0}: {1} is not a map.
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/.
WSWS3150E: Error: No provider type matches QName ''{0}''
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/.
WSWS3151E: Error: No operation name specified.
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/.
WSWS3152E: Error: Cannot find operation: {0} - none defined
Problem The WSDL does not define any operations in the portType.
User response This is an internal error or deployment error.
WSWS3153E: Error: Cannot find operation: {0}
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/.
WSWS3154E: Error: No ''{0}'' option was configured for the service ''{1}''
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/.
WSWS3155E: Error: {0} not found as an input part OR an output part.
Problem The parameter order attribute must reference a message part.
User response Correct the WSDL.
WSWS3156E: Error: Cannot find port: {0}
Problem The specified port could not be found by Service.getPort.
User response Correct the invocation of Service.getPort.
WSWS3157E: Error: Cannot find portType: {0}
Problem The deployed wsdl is missing the portType.
User response Correct the deployed wsdl.
WSWS3158E: Error: No request message in MessageContext?
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/.
WSWS3159E: Error: No serializer found for class {0} in registry {1}
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/.
WSWS3160E: Error: Cannot find service: {0}
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/.
WSWS3161E: Error: No service has been defined.
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/.
WSWS3162E: Error: No service object defined for this Call object.
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/.
WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is {0}
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/.
WSWS3164E: Error: No security provider in MessageContext.
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/.
WSWS3165E: Error: No HTTP SOAPAction property in context.
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/.
WSWS3166E: Error: No client transport named ''{0}'' found.
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/.
WSWS3167E: Error: No transport mapping for protocol: {0}
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/.
WSWS3168E: Error: No mapped schema type for {0}
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/.
WSWS3169E: Error: Component requires a type attribute.
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/.
WSWS3170E: Error: Must include type attribute for Handler deployment!
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/.
WSWS3171E: Error: No type QName for mapping!
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/.
WSWS3172E: Error: User ''{0}'' not authorized to ''{1}''
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/.
WSWS3173E: Error: Did not understand "MustUnderstand" header(s):{0}
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/.
WSWS3174E: Error: No value field for RPCParam to use. {0}
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/.
WSWS3175E: Error: {0} is null.
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/.
WSWS3176E: Error: AdminClient did not initialize correctly: ''call'' is null!
Problem Internal Error.
User response AdminClient is not fully supported.
WSWS3177E: Error: Null namespace URI specified.
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/.
WSWS3178E: Error: null parent.
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/.
WSWS3179E: Error: Null provider type passed to WSDDProvider.
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/.
WSWS3180E: Error: Null response 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/.
WSWS3181E: Error: Odd number of digits in hex string.
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/.
WSWS3182E: Error: Only one Body element allowed in SOAPEnvelope.
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/.
WSWS3183E: Error: Only one Header element allowed in SOAPEnvelope.
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/.
WSWS3184E: Error: Number of parameters passed in ({0}) doesn''t match the number of IN/INOUT parameters ({1}) from the addParameter() calls.
Problem The number of parameters does not match the expected number of parameters.
User response This could be a DII or internal error.
WSWS3185I: Info: Parsing XML file: {0}
Problem informational message.
User response no action required.
WSWS3186E: Error: Error in parsing: {0}
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/.
WSWS3187E: Error: Processing file {0}
Problem AdminClient error processing the indicated file.
User response AdminClient is not fully supported.
WSWS3188I: Info: {0} quitting.
Problem informational message.
User response no action required.
WSWS3189E: Error: Administration service requested to quit, quitting.
Problem Admin quitting.
User response Admin class is not fully supported.
WSWS3190E: Error: Unable to bind to port {0}. Did not start SimpleServerEngine.
Problem Internal Error.
User response SimpleServerEngine not fully supported.
WSWS3191I: Info: Configuration file read-only so engine configuration changes will not be saved.
Problem informational message.
User response no action required.
WSWS3192E: Error: return code: {0} {1}.
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/.
WSWS3193E: Error: Problem with servlet engine /WEB-INF directory
Problem /WEB-INF may not be accessible.
User response Correct problem with WEB-INF directory.
WSWS3194E: Error: Problem with servlet engine config file: {0}
Problem config file may not be accessible.
User response Correct problem with servlet engine config file.
WSWS3195W: Warn: Unable to load/create servlet engine config file, attempting internal default (from jar).
Problem This exception is unexpected. The cause is not immediately known.
User response no action required.
WSWS3196E: Error: Problem with servlet engine config file (loading from jar).
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/.
WSWS3197I: Info: {0} starting up on port {1}.
Problem informational message.
User response no action required.
WSWS3198E: Error: Type/Element attribute on Part ''{0}'' is not set.
Problem The WSDL part must specify the type or element attribute.
User response Correct the deployed wsdl.
WSWS3199E: Error: Unexpected end of stream.
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/.
WSWS3200E: Error: Unknown host - could not verify administrator access.
Problem Unknown host encountered by Admin tool.
User response The Admin tool is not fully supported.
WSWS3201E: Error: Where {0} looks like:
Problem Admin tool error.
User response Admin tool is not fully supported.
WSWS3202E: Error: Error processing WSDL document: {0} {1}
Problem Normally an error with the deployed wsdl detected during service creation.
User response Correct the deployed wsdl.
WSWS3203E: Error: Missing WSDL document in Service.getPort.
Problem A WSDL document is needed if you want to use Service.getPort.
User response Correct your deployment information.
WSWS3204E: Error: {0} already exists.
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/.
WSWS3205E: Error: Type {0} is referenced but not defined.
Problem Your wsdl references types or elements that are not defined.
User response Correct your wsdl.
WSWS3206E: Error: Cannot find EJB at JNDI location {0}
Problem There may be a problem with your JNDI configuration.
User response Correct your JNDI configuration.
WSWS3207E: Error: Cannot create InitialContext.
Problem An InitialContext was not created.
User response Inspect other errors to determine why InitialContext was not created.
WSWS3208E: Error: The definition of {0} results in a loop.
Problem Found recursive definition of the indicated type or element.
User response Correct your wsdl.
WSWS3209E: Error: Bad property. The value for {0} should be of type {1}, but it is of type {2}.
Problem A bad property detected on the Call or MessageContext. This could be caused by an internal error.
User response Fix the property.
WSWS3210E: Error: Null property name specified.
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/.
WSWS3211E: Error: Null property value specified.
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/.
WSWS3212E: Error: Property name {0} not supported.
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/.
WSWS3213E: Error: Null getter method specified.
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/.
WSWS3214E: Error: Null setter method specified.
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/.
WSWS3215E: Error: Null public instance field specified.
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/.
WSWS3216E: Error: Null java class specified in TypeMappingImpl.isRegistered method.
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/.
WSWS3217E: Error: Null qualified name specified in TypeMappingImpl.isRegistered method.
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/.
WSWS3218E: Error: Null serializer factory specified in the TypeMappingImpl.register method.
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/.
WSWS3219E: Error: Error: Message part {0} of operation or fault {1} is specified as a type and the soap:body use of binding "{2}" is literal. This WSDL is not currently supported.
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/.
WSWS3220E: Error: Error: Empty or missing service name.
Problem The WSDL service name is wrong.
User response Correct the WSDL.
WSWS3221E: Error: Bean attribute {0} is of type {1}, which is not a simple type.
Problem Attributes must be simple types.
User response Correct the WSDL.
WSWS3222E: Error: Attribute is of type {0}, which is not a simple type.
Problem Attributes must be simple types.
User response Correct the WSDL.
WSWS3223E: Error: Exception caught while constructing handler {0}: {1}
Problem Problem creating JAXRPC Handler.
User response Review reasons for thrown exception.
WSWS3224I: Info: No disk access, using memory only.
Problem informational message
User response No action required.
WSWS3225E: Error: No DeserializerFactory for {0}
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/.
WSWS3226E: Error: Null FieldDesc specified.
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/.
WSWS3227E: Error: Exception:
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/.
WSWS3228E: Error: Exception: {0}
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/.
WSWS3229E: Error: ConfigurationException:
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/.
WSWS3230E: Error: ParserConfigurationException:
Problem Indicates that an error has occurred while configuring the xml parser.
User response Correct the parser configuration.
WSWS3231E: Error: SAXException:
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.
WSWS3232E: Error: java.net.UnknownHostException:
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/.
WSWS3233E: Error: javax.mail.MessagingException:
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/.
WSWS3234E: Error: java.io.IOException:
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/.
WSWS3235E: Error: java.io.IOException: {0}
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/.
WSWS3236E: Error: IllegalAccessException:
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/.
WSWS3237E: Error: IllegalArgumentException:
Problem This may be issued during overloaded message processing.
User response This exception is unexpected. The cause is not immediately known.
WSWS3238E: Error: IllegalArgumentException: {0}
Problem This error may occur during overloaded method processing.
User response This exception is unexpected. The cause is not immediately known.
WSWS3239E: Error: InvocationTargetException:
Problem A problem occurred invoking the indicated target.
User response This exception is unexpected. The cause is not immediately known.
WSWS3240E: Error: InstantiationException:
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/.
WSWS3241E: Error: MalformedURLException:
Problem Malformed URL Exception occurred in the SimpleServerEngine.
User response This exception is unexpected. The cause is not immediately known.
WSWS3242E: Error: WebServicesFault:
Problem A WebServicesFault has occurred.
User response See other messages for more detailed information.
WSWS3243I: Info: Mapping Exception to WebServicesFault.
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.
WSWS3244I: Info: Mapping Exception to WebServicesFault: {0}
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.
WSWS3245E: Error: WSDL2Java emitter timed out (this often means the WSDL at the specified URL is inaccessible)!
Problem Normally indicates that the WSDL is not accessible.
User response Make sure the WSDL is accessible.
WSWS3246E: Error: SOAPFault.addDetail called when a detail is present.
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/.
WSWS3247E: Error: No endpoint.
Problem See other messages for more details.
User response This exception is unexpected. The cause is not immediately known.
WSWS3248E: Error: Unsupported attachment type "{0}" only supporting "{1}".
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/.
WSWS3249E: Error: This attachment implementation accepts only SOAPPart objects as the root part.
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/.
WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.
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/.
WSWS3251E: Error: Stream closed.
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/.
WSWS3252E: Error: End of stream encountered before final boundary marker.
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/.
WSWS3253E: Error: maxCached value is bad: {0}
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/.
WSWS3254E: Error: Reset and mark not 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/.
WSWS3255E: Error: input buffer is null.
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/.
WSWS3256E: Error: Offset is negative: {0}
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/.
WSWS3257E: Error: Length: {0}
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/.
WSWS3258E: Error: Write beyond buffer.
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/.
WSWS3259E: Error: Error reading data stream: {0}
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/.
WSWS3260E: Error: File for data handler does not exist: {0}
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/.
WSWS3261E: Error: Error in MIME data stream, start boundary not found, expected: {0}.
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/.
WSWS3262E: Error: Error in parsing mime data stream: {0}.
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/.
WSWS3263E: Error: No support for attachments.
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/.
WSWS3264E: Error: No content.
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/.
WSWS3265E: Error: No engine configuration file - aborting.
Problem Possibly an internal error.
User response Make sure your engine configuration is correct.
WSWS3266E: Error: The element "{0}" is an attachment with sub elements which is not supported.
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/.
WSWS3267E: Error: Error: Missing type resolution for element {2}, in WSDL message part {0} of operation {1}.
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/.
WSWS3268E: Error: The soap:operation for binding operation {0} must have a "use" attribute.
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/.
WSWS3269E: Error: Default type mapping cannot be modified.
Problem The type mapping cannot be modified after registration has occurred.
User response Please correct your code.
WSWS3270E: Error: Type mapping cannot be modified via delegate.
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/.
WSWS3271E: Error: Invalid TypeMapping specified: wrong type or null.
Problem Invalid TypeMapping registration.
User response Please correct your code.
WSWS3272E: Error: Default type mapping from secondary type mapping registry is already in use.
Problem Cannot change default type mapping after registration.
User response Please correct your code.
WSWS3273E: Error: There is no stub implementation for the interface:
Problem You cannot call this getPort method because there is no stub implementation of the interface.
User response Please change your code.
WSWS3274E: Error: {0}: {1} is not a vector.
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/.
WSWS3275E: Error: Invalid parameter mode byte ({0}) passed to getModeAsString().
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/.
WSWS3276E: Error: Marking streams not 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/.
WSWS3277E: Error: Could not resolve to an operation. The message contains an element named ""{0}"", but this does not match any operation of the target port. Debug: {1}
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/.
WSWS3278E: Error: Attempt to set implementation class on a ServiceDesc which has already been configured.
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/.
WSWS3279E: Error: Unable to create JavaBean of type {0}. Missing default constructor? Error was: {1}.
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/.
WSWS3280E: Error: The value of -soapAction must be DEFAULT, NONE or OPERATION.
Problem A bad argument was specified for -soapAction.
User response Use the correct Java2WSDL -soapAction option.
WSWS3281E: Error: Tried to invoke method ''{0}'' with argument classes ''{1}'' against object ''{2}'' of class ''{3}''. The arguments do not match the signature.
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/.
WSWS3282I: Info: Generating {0}.
Problem Informational message indicating which java classes are generated by WSDL2Java.
User response no action required.
WSWS3283E: Error: The value of -style must be DOCUMENT or RPC.
Problem The -style option of Java2WSDL is incorrect.
User response Use a correct -style option.
WSWS3284E: Error: Could not find class ''{0}'' for the service.
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/.
WSWS3285E: Error: Could not find class ''{0}'' for the service ''{1}''.
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/.
WSWS3286E: Error: The <class-of-portType> has already been specified as, {0}. It cannot be specified again as {1}.
Problem Only one class file may be specified for Java2WSDL.
User response Correct your invocation of Java2WSDL.
WSWS3287E: Error: The <class-of-portType> was not specified.
Problem A class file must be specified for Java2WSDL.
User response Correct your invocation of Java2WSDL.
WSWS3288E: Error: The wsdl URI has already been specified as, {0}. It cannot be specified again as {1}.
Problem The WSDL file can only be specified once for WSDL2Java.
User response Correct your invocation of WSDL2Java.
WSWS3289E: Error: The wsdl URI was not specified.
Problem The WSDL URI must be specified for WSDL2Java.
User response Correct your invocation of WSDL2Java.
WSWS3290E: Error: Unrecognized {0}: ''{1}''
Problem Inappropriate value for the enumeration.
User response Please correct your code.
WSWS3291E: Error: The class {0} is not a bean class and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
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.
WSWS3292W: Warning: The class {0} is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
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.
WSWS3293E: Error: The class {0} does not contain a default constructor, which is a requirement for a bean class. The class cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
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.
WSWS3294E: Error: The XML Schema type ''{0}'' is not currently supported.
Problem WSDL2Java does not support this XML Schema type.
User response Correct your wsdl.
WSWS3295E: Error: Message part {0} of operation or fault {1} has no element or type attribute.
Problem Each message part must have an element or type attribute which locates the schema element/type.
User response Correct your wsdl.
WSWS3296E: Error: The value of {0} for attachment format must be {1};
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/.
WSWS3297E: Error: DIME Type length is {0} which exceeds maximum {0}
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/.
WSWS3298E: Error: DIME ID length is {0} which exceeds maximum {1}.
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/.
WSWS3299E: Error: Max chunk size "{0}" needs to be greater than one.
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/.
WSWS3300E: Error: Max chunk size "{0}" exceeds 32 bits.
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/.
WSWS3301E: Error: Each DIME Stream must be read fully or closed in succession.
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/.
WSWS3302E: Error: DIME stream data not padded correctly.
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/.
WSWS3303E: Error: Received "{0}" bytes to read.
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/.
WSWS3304E: Error: Received "{0}" as an offset.
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/.
WSWS3305E: Error: Array to read is null.
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/.
WSWS3306E: Error: Array size of {0} to read {1} at offset {2} is too small.
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/.
WSWS3307E: Error: End of physical stream detected when more DIME chunks expected.
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/.
WSWS3308E: Error: End of physical stream detected when {0} more bytes expected.
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/.
WSWS3309E: Error: There are no more DIME chunks expected!
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/.
WSWS3310E: Error: DIME header less than {0} bytes.
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/.
WSWS3311E: Error: DIME version received "{0}" greater than current supported version "{1}".
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/.
WSWS3312E: Error: DIME option length "{0}" is greater stream length.
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/.
WSWS3313E: Error: DIME stream closed during options padding.
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/.
WSWS3314E: Error: DIME stream closed getting ID length.
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/.
WSWS3315E: Error: DIME stream closed getting ID padding.
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/.
WSWS3316E: Error: DIME stream closed getting 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/.
WSWS3317E: Error: DIME stream closed getting type padding.
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/.
WSWS3318E: Error: DIME stream received bad type "{0}".
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/.
WSWS3319E: Error: A holder could not be found or constructed for the OUT parameter {0} of method {1}.
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/.
WSWS3320E: Error: Illegal argument passed to ParameterDesc.setJavaType. The java type {0} does not match the mode {1}.
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/.
WSWS3321E: Error: Invalid normalizedString value.
Problem The NormalizedString object could not be set due to an invalid value.
User response Correct the normalizedString value.
WSWS3322E: Error: Invalid token value.
Problem The Token object could not be set due to an invalid value.
User response Correct the token value.
WSWS3323E: Internal Error occurred while build the property descriptors for {0}.
Problem Internal Error.
User response Make sure the indicate class complies with JAX-RPC.
WSWS3324E: Error: Problems encountered trying to write schema for {0}
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/.
WSWS3325E: Error: Error looking for parameter names in bytecode: input does not appear to be a valid class file.
Problem You probably specified an invalid class to Java2WSDL.
User response Correct the indicated class.
WSWS3326E: Error: Error looking for parameter names in bytecode: unexpected end of file.
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/.
WSWS3327E: Error: Error looking for parameter names in bytecode: unexpected bytes in file.
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/.
WSWS3328E: Error: The class {0} extends non-bean class {1}. An xml schema anyType will be used to define {0} in the wsdl file.
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.
WSWS3329E: Error: The XML Schema type ''{0}'' is not valid in the Schema version ''{1}''.
Problem WSDL2Java error.
User response Please correct your wsdl.
WSWS3330I: Info: {0} already exists, WSDL2Java will not overwrite it.
Problem WSDL2Java informational message.
User response No action required.
WSWS3331E: Error: Invalid gYearMonth: {0}
Problem Error occurred while constructing a YearMonth object.
User response Use a correct value.
WSWS3332E: Error: Invalid gYear: {0}
Problem Error occurred while constructing a Year object.
User response Use a correct value.
WSWS3333E: Error: Invalid gMonth: {0}
Problem Error occurred while constructing a Month object.
User response Use a correct value.
WSWS3334E: Error: Invalid gDay: {0}
Problem Error occurred while constructing a Day object.
User response Use a correct value.
WSWS3335E: Error: Invalid gMonthDay: {0}
Problem Error occurred while constructing a MonthDay object.
User response Use a correct value.
WSWS3336E: Error: Invalid duration: must contain a P.
Problem Error occurred while constructing a Duration object.
User response Use a correct value.
WSWS3337E: Error: Serializer class {0} does not implement SimpleValueSerializer, which is necessary for attributes.
Problem This serializer cannot be used to serialize attributes.
User response Please correct your deployed type mappings.
WSWS3338E: Error: JIMI is necessary to use java.awt.Image attachments (http://java.sun.com/products/jimi/).
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/.
WSWS3339E: Error: javax.xml.transform.Source implementation not supported: {0}.
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/.
WSWS3340E: Error: The OperationDesc for {0} was not synchronized to a method of {1}.
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/.
WSWS3341E: Error: No service class was found.
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/.
WSWS3342E: Error: Cannot handle {0}, can only handle JPEG image types.
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/.
WSWS3343W: Warning: Factory {0} Ignored: missing required method: {1}.
Problem Correct your factory implementation.
User response This exception is unexpected. The cause is not immediately known.
WSWS3344W: Warning: Factory {0} Ignored: invoke method failed: {1}.
Problem Invoke method failed.
User response This exception is unexpected. The cause is not immediately known.
WSWS3345E: Error: Unable to locate a valid EngineConfigurationFactory.
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/.
WSWS3346E: Error: Factory {0} Ignored: unable to load/resolve class.
Problem Cannot load the indicated factory.
User response Make sure that the factory can be loaded.
WSWS3347E: Error: classname attribute is missing.
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/.
WSWS3348E: Error: qname attribute is missing.
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/.
WSWS3349E: Error: Element {0} is referenced but not defined.
Problem WSDL2Java error indicating that an element is referenced but no definition was found.
User response Please correct your wsdl.
WSWS3350E: Error: Missing type or ref attribute for node ''{0}''
Problem A type or ref attribute is used to reference a type or element.
User response Please correct your wsdl.
WSWS3351E: Error: Unable to deploy typemapping: {0}
Problem This may be due to a deployment problems.
User response Make sure that the indicated class can be found and loaded.
WSWS3352E: Error: Couldn''t find a matching Java operation for WSDD operation "{0}" ({1} args).
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/.
WSWS3353E: Error: Method style for message-based service wasn't one we recognized.
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/.
WSWS3354E: Error: Method ''{0}'' does not match any of the valid signatures for message-style service methods.
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/.
WSWS3355E: Error: unmatchedOp=Binding operation has no corresponding portType operation: name = {0}, input name = {1}, output name = {2}
Problem An invalid binding operation was encountered in the wsdl.
User response Please correct the wsdl.
WSWS3356E: Error: Couldn't find an appropriate operation for XML QName {0}
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/.
WSWS3357E: Error: while trying to deserialize operation {0}, an element named {1} was encountered. However, this element does not match any of the expected parameters for this operation. Here is the list of expected parameters: {2}
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.
WSWS3358E: Error: ERROR: Unable to match binding fault "{0}" from binding {2}, operation "{1}", to a PortType fault.
Problem The binding fault must have a corresponding portType fault.
User response Please correct the wsdl
WSWS3359E: Error: Fault is missing a name= attribute in operation "{0}", in binding {1}.
Problem The binding fault must have a name.
User response Please correct the wsdl.
WSWS3360E: Error: ERROR: Missing {soap:fault} element inFault "{0}" in operation "{1}", in binding {2}
Problem The binding fault must have an appropriate {soap:fault} element.
User response Please correct the wsdl.
WSWS3361E: Error: Found instance data for {0} in the soap:body instead of the soap:header.
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/.
WSWS3362E: Error: Didn''t find specified return QName {0}
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/.
WSWS3363E: Error: The value of the -use option must be LITERAL or ENCODED.
Problem The -use option of Java2WSDL is incorrect.
User response Correct the -use option.
WSWS3364E: Error: Invalid class provided for -extraClasses option: {0}
Problem The -extraClasses option of Java2WSDL is incorrect.
User response Correct the -extraClasses option.
WSWS3365E: Error: Cannot invoke a oneway call when the call has a return type.
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.
WSWS3366E: Error: The operation must be specified.
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/.
WSWS3367E: Error: Failure priming the MessageContext object for operation invocation: {0}
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/.
WSWS3368E: Error: The deserialization event {0} for ({1}) was unexpected in {2}.
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/.
WSWS3369E: Error: The builder {0} does not have a SOAPElement to build.
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/.
WSWS3370E: Error: Only one SOAPEnvelope is allowed in a SOAPFactory.
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/.
WSWS3371E: Error: Cannot invoke addChildElement on a {0} object.
Problem Cannot add a child SOAPElement to the indicated object.
User response Correct your code.
WSWS3372E: Error: Cannot add a {0} child element to a {1} object.
Problem Cannot add the indicated child element.
User response Correct your code.
WSWS3373E: Error: Cannot invoke addTextNode on a {0} object.
Problem Cannot add a Text node to the indicated object.
User response Correct your code.
WSWS3374E: Error: Cannot replace SOAPElement's attributes.
Problem Cannot call setAttributes after the SOAPElement has attributes.
User response Correct your code.
WSWS3375E: Error: Cannot replace SOAPElement's MappingScope.
Problem Cannot call setMappingScope after the SOAPElement has a MappingScope.
User response Correct your code.
WSWS3376E: Error: Don't know how to convert alternate content of class {0}.
Problem This is an unrecognized alternate content type.
User response Correct your code.
WSWS3377E: Error: Multiple elements have the name ({0}):{1}.
Problem Expecting only one child element of the given qname.
User response Correct your code.
WSWS3378E: Error: Can't set alternate content on a SOAPElement that already has alternate content.
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.
WSWS3379E: Error: Prefix {0} is undefined.
Problem The indicated prefix does not have a corresponding namespace uri.
User response Correct your code or soap message.
WSWS3380E: Error: An attempt was made to modify a read-only MappingScope.
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/.
WSWS3381E: Error: Circular loop encountered while processing MappingScope.
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/.
WSWS3382E: Error: An unqualified namespace cannot have a prefix. Prefix is {0}.
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/.
WSWS3383E: Error: Illegal use of xmlns prefix encountered: {0}
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/.
WSWS3384E: Error: Admin process failed.
Problem Admin tool failed.
User response The Admin tool is not fully supported.
WSWS3385E: Error: The onStartChild method of {0} did not return a processor.
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/.
WSWS3386E: Error: Tried to push a null processor.
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/.
WSWS3387E: Error: An attempt was made to serialize a null object. This should have been handled in the serialize() method.
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/.
WSWS3388E: Error: Exception generated while rewinding request handlers during fault processing: exception ignored, processing halted.
Problem An exception was thrown during handler fault processing.
User response Inspect your handlers.
WSWS3389E: Error: JAXRPC Handler Class {0} not found/loaded, ignored.
Problem The indicated class could not be found and/or loaded.
User response Determine why the class was not found or loaded.
WSWS3390E: Error: Load of class {0} failed unexpectedly.
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/.
WSWS3391W: Warn: {0}.handleRequest returned false and failed to set response message.
Problem Warning.
User response This exception is unexpected. The cause is not immediately known.
WSWS3392E: Error: Unexpected: Unable to create response message on behalf of handler.
Problem Warning.
User response This exception is unexpected. The cause is not immediately known.
WSWS3393E: Error: {0}.handlerRequest should not throw javax.xml.rpc.soap.SOAPFaultException on client-side.
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/.
WSWS3394E: Internal Error: attempted to put {0} into pool of {1}.
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/.
WSWS3395E: Error: {0}.{1} threw RuntimeException.
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/.
WSWS3396E: Error: Handler {0}: Protected state violation. (JSR 109, Web services for J2EE, Version 1.0, 6.2.2.2).
Problem Tried to illegally manipulate xml.
User response Correct your handler.
WSWS3397E: Error: JSR-109 requires that Service.getHandlerRegistry() throw an UnsupportedOperationException in a managed container.
Problem Cannot call this method in a managed container.
User response Correct your handler.
WSWS3398E: Error: JSR-109 requires that Service.getTypeMappingRegistry() throw an UnsupportedOperationException in a managed container.
Problem Cannot call this method in a managed container.
User response Correct your handler.
WSWS3399E: Error: {0} ''{1}'' didn't implement ''{2}''.
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/.
WSWS3400I: Info: unexpected exception.
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/.
WSWS3401E: Error: RequestMessage missing on MessageContext.
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/.
WSWS3402E: Error: INTERNAL: ResponseMessage missing on MessageContext.
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/.
WSWS3403E: Error: Unexpected Life Cycle State: current="{0}", expected="{1}".
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/.
WSWS3404E: Error: Unexpected: SubSet({0}, {1}, {2}): acting as empty set.
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/.
WSWS3405I: Info: Ignoring exception thrown by {0}.
Problem Informational Message.
User response No action required.
WSWS3406E: Unexpected exception caught while sending reply message: {0}
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/.
WSWS3407E: Invalid protocol for JMS URL string: {0}
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.
WSWS3408E: A valid URL string can not be formed from the properties contained in the JMSURLParser object. Linked exception: {0}
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.
WSWS3409E: Internal Error: Client/Server mode not set for soap port.
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/.
WSWS3410E: Invalid value specified for the {0} property.
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.
WSWS3411E: Request timeout exceeded.
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.
WSWS3412E: A JMS reply message was received which did not correlate with the JMS request message.
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/.
WSWS3413E: The JMS reply message was not of the correct JMS message type.
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/.
WSWS3414E: Style DOCUMENT, Use LITERAL, and Wrapped do not allow operation {0} to be overloaded.
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/.
WSWS3415E: Buffer size <= 0
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/.
WSWS3416E: Stream closed.
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/.
WSWS3417W: Response set in MessageContext for a one-way message. Reponse will be ignored.
Problem Runtime set a response message onto the MessageContext for a one-way message.
User response Correct JAXRPC Handler logic.
WSWS3418E: Error: Exception generated during handler fault processing.
Problem An exception was thrown during handler fault processing.
User response Inspect your handlers.
WSWS3419E: The current node is not a Text node, and it either has more than one child node or has a child node that is not a Text node.
Problem It's not allowed to set a value the node as described in the exception.
User response =CMSG0002
WSWS3420E: Error: Emitter failure. Part {0} of operation {1} must be a type part.
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.
WSWS3421E: Error: The service interface ''{0}'' does not subclass ''javax.xml.rpc.Service''.
Problem The specified interface must subclass ''javax.xml.rpc.Service''.
User response Specify an interface that subclasses ''javax.xml.rpc.Service''.
WSWS3422E: Error: Can not instantiate {0}.
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
WSWS3423E: Error: "javax.xml.soap.write-xml-declaration" property has to be either true or false.
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/.
WSWS3424E: Error: List value of type {1}, is not a simple type.
Problem xsd:list itemTypes must be atomic values.
User response Correct the WSDL.
WSWS3425I: From target realm: {0}.
Problem informational message.
User response no action required.
WSWS3426I: HTTP Basic Authentication information has been received.
Problem informational message.
User response no action required.
WSWS3427I: No HTTP Basic Authentication Information has been received.
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.
WSWS3428W: Warning: Found an old J2EE 1.3 version of the DD. A new J2EE 1.4 version will be written.
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.
WSWS3429W: Warning: Found old J2EE 1.3 {0} file. This indicates a version mismatch - a new J2EE 1.4 DD will be written.
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.
WSWS3430E: Invalid CharacterEncoding: {0}.
Problem Expected valid CharacterEncoding for incoming message.
User response Correct CharacterEncoding for incoming message.
WSWS3431E: Error: No Service Endpoint Class found for port {0}.
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/.
WSWS3432E: Error: Exception thrown while invoking method ''{0}'' against object ''{2}'' of class ''{3}''.
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/.
WSWS3433E: Internal Error: No Processor assigned to port {0}.
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/.
WSWS3434E: Unable to load configuration file
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/.
WSWS3435E: Error: Invalid date/time. Received an empty string for a date/time value.
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/.
WSWS3436E: Error: Invalid time: Received an empty string for a time value.
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/.
WSWS3437E: Error: Invalid date: Received an empty string for a date value.
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/.
WSWS3438E: Error: The service locator ''{1}'' does not subclass the service interface ''{0}''.
Problem The specified service locator must subclass the service interface.
User response Specify a service locator that subclasses the service interface.
WSWS3439E: Error: The contents of the SOAP body are encrypted. The target operation cannot be invoked. The body contains an element with the name: {0}.
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/.
WSWS3440W: Warning: The WSDL2Java emitter does not understand qname {0} specified in field {1} of construct {2} in the mapping file: {3}. The information in the mapping file corresponding to this qname will be ignored.
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
WSWS3442E: Error: No output for Call.{0}.
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.
WSWS3443E: Handler {0}: Protected state violation: SOAPPart missing/removed.
Problem Improper use of JAX-RPC API in handler.
User response Review and correct use of JAX-RPC APIs.
WSWS3444E: Handler {0}: Protected state violation: SOAPMessage missing/removed.
Problem Improper use of JAX-RPC API in handler.
User response Review and correct use of JAX-RPC APIs.
WSWS3445E: Handler {0}: Protected state violation: Unexpected exception. Review error log for details.
Problem Improper use of JAX-RPC API in handler.
User response Review and correct use of JAX-RPC APIs.
WSWS3446E: The endpoint address URL is missing.
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.
WSWS3447E: Error: Could not get a secure socket factory with the SSL settings of JSSE.
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.
WSWS3448I: Info: HTTP Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
Problem Configured HTTP proxy information.
User response None.
WSWS3449I: Info: HTTPS Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
Problem Configured HTTPS proxy information.
User response None.
WSWS3450I: Info: SSL configuration is from {0}.
Problem Specified SSL configuration. It can be by a java property file, a SSL configuration alias, or the JSSE SSL settings.
User response None.
WSWS3451I: Info: Response from Proxy for HTTP CONNECT: {0}.
Problem HTTP response from Proxy for the HTTP CONNECT request
User response None.
WSWS3452E: Internal Error: Attempted to generate code without first parsing WSDL file.
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/.
WSWS3453I: File {0} will NOT be written. Write permission denied by underlying file system.
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.
WSWS3454E: Mixture of different settings for 'style/use' within a WSDL binding is NOT supported. Inconsistent values for the "{0}" binding are: {1}={2} and {3}={4}
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.
WSWS3455I: Error: Invalid -javaSearch option argument "{0}". Valid options are "File", "Classpath", or "Both". Defaulting to "File".
Problem The -javaSearch option of WSDL2Java is wrong.
User response Correct the -javaSearch option setting.
WSWS3456E: Error: The onStartChild method of {0} does not know understand how to process element {1}. Processing cannot continue.
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/.
WSWS3457W: Warning: The WSDL2Java emitter has found relative namespace {0} in the WSDL, and cannot transform it to an absolute namespace.
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.
WSWS3458E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible return types found at SEI method: "{0}" Existing Java return type = {1} WSDL defined return type = {2}
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.
WSWS3459E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible parameter types found at SEI method: "{0}" Existing Java parameter type = {1} WSDL defined parameter type = {2}
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.
WSWS3460E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible field types found in Java class: "{0}" Existing Java class field type = {1} WSDL defined field type = {2}
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.
WSWS3461E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Enumeration class is invalid: "{0}" Missing the following JAX-RPC required method = {1}
Problem Validation Error. An existing Enumeration class is missing a required method.
User response Add the specified method to the Enumeration class.
WSWS3462E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Enumeration class is invalid: "{0}" Contains invalid method = {1}
Problem Validation Error. An existing Enumeration class contains an invalid method.
User response Remove specified method from the Enumeration class.
WSWS3463E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" Does NOT contain a public default constructor = {1}
Problem Validation Error. An existing Bean class does not contain required default constructor.
User response Add a default constructor to specified Bean.
WSWS3464E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" It extends a non-bean class = {1}
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.
WSWS3465E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" It does not define a bean property for the following data member = {1}
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.
WSWS3466E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Fault class is invalid: "{0}" It does not extend = {1}
Problem Validation Error. Specified fault class is not a Java Exception class.
User response Make the specified fault class extend java.lang.Exception.
WSWS3467E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Fault class is invalid: "{0}" Does not implement a valid public constructor: "{1}", containing {2} parameters.
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.
WSWS3468E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Fault class is invalid: "{0}" It does not define a property for the following data member = {1}
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.
WSWS3469E: ---------- WSDL2Java VALIDATION ERROR ---------- Incompatible parameter types found at Fault class method: "{0}" Existing Java parameter type = {1} WSDL defined parameter type = {2}
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.
WSWS3470E: Error while running class ''{0}''.
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/.
WSWS3471W: Binding {0} has already been generated and will not be re-generated.
Problem None.
User response None.
WSWS3472W: One-way operations were requested for methods returning 'void', but operation ''{0}'' has been declared to throw a fault, so it will be converted into a two-way operation.
Problem None.
User response None.
WSWS3473E: No binding generator was found for binding type ''{0}''.
Problem An unsupported binding type was requested.
User response Ensure that only valid binding types are requested.
WSWS3474I: Found a binding generator for binding type ''{0}''.
Problem None.
User response None.
WSWS3475W: A binding specific location property was not specified for the requested {0} binding. The default location ''{1}'' will be used.
Problem None.
User response None.
WSWS3476W: The generic -location option should not be used when more than one binding type has been requested.
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.
WSWS3477I: Binding-specific properties are {0}
Problem None.
User response None.
WSWS3479E: The ''{0}'' property is required, but was not specified.
Problem Required property needs to be specified.
User response Specify required property.
WSWS3480E: One or more errors occurred while validating the input properties.
Problem See previously reported errors.
User response Fix cause of previously reported errors.
WSWS3481E: There is no binding defined for {0} RequestSender.
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/.
WSWS3482E: There is no deployment descriptor defined for {0} RequestSender.
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/.
WSWS3483E: Could not find WSDL file ''{0}'' within the EAR.
Problem WSLD file could not be found where it was expected.
User response Fix the EAR.
WSWS3484E: Caught {0} while trying to read WSDL file ''{1}'': {2}
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/.
WSWS3485E: No WSDL services were found for namespace ''{0}''.
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/.
WSWS3486E: The ClassLoader parameter was passed in as null.
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.
WSWS3487E: The port name and service ref name are both null.
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/.
WSWS3488E: Error: This SOAPElement is not a swaRef - it is not a reference to an attachment.
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.
WSWS3489E: Error: Mime type {0} does not match object type {1}.
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.
WSWS3490E: Error: The system cannot load the file referenced within {0}. The problem is with {1}.
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.
WSWS3491E: Error: Reading import file: {0}
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.
WSWS3492W: Warning: Invalid option combination: style={0} and use={1} Will default to 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
WSWS3493E: Error: Invalid combination: style="{0}" and use="{1}" For binding="{2}" and binding operation="{3}"
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
WSWS3494I: syncTimeout value is {0} seconds to wait for response to the current SOAP over {1} request.
Problem Configured syncTimeout value in seconds.
User response None.
WSWS3495I: {0} is used as the final endpoint address.
Problem None.
User response None.
WSWS3496I: {0} is used as the proxy address.
Problem None.
User response None.
WSWS3497I: Status in the HTTP response: {0}, {1}
Problem Inform the HTTP response from the server.
User response None.
WSWS3498E: No HTTP status has been received for the current HTTP response.
Problem No HTTP status information is available to determine the HTTP response.
User response Make sure the target HTTP server is up.
WSWS3499W: Redirected new location: {0}
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.
WSWS3500I: Required service: {0} from JNDI namespace: {1}
Problem None.
User response None.
WSWS3501E: Failures from the Channel Framework service: {0}
Problem There are failures from the Channel Framework service.
User response Check errors reported by Channel Framework service in the log.
WSWS3502E: Unsupported schema for HTTP: {0}
Problem Found unsupported schema for using HTTP transport.
User response Verify the target endpoint address.
WSWS3503I: Updated configuration of the outbound connection for key: {0}
Problem None.
User response None.
WSWS3504E: Failed to retrieve HTTP(S) proxy information for the proxy connection.
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.
WSWS3505I: Creating channel named: {0}
Problem None.
User response None.
WSWS3506I: Found channel named: {0}
Problem None.
User response None.
WSWS3507I: Creating channel chain named: {0}
Problem None.
User response None.
WSWS3508I: Found channel chain named: {0}
Problem None.
User response None.
WSWS3509I: Expect 100 Continue in the HTTP response...sending HTTP request headers only to connection: {0}
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.
WSWS3510I: Sending both HTTP request headers and body message to connection: {0}
Problem None.
User response None.
WSWS3511I: Sending current request to {0} in version: {1}
Problem Sending current SOAP over HTTP request in indicated HTTP version.
User response None.
WSWS3512E: Unsupported HTTP version: {0}
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/.
WSWS3513E: Invalid HTTP response received from the connection for: {0}
Problem Invalid HTTP response is received. This could be an internal error.
User response None.
WSWS3514E: No HTTP response body is available from the connection for: {0}
Problem There are failures with the HTTP Channel service.
User response Check errors reported by HTTP Channel service in the log.
WSWS3515E: Failures with the SSL Channel services: {0}
Problem There are failures with the SSL Channel service.
User response Check errors reported by SSL Channel service in the log.
WSWS3516I: Received cookie for HTTP header: {0} in the response from connection to: {1}
Problem None.
User response None.
WSWS3517I: Target address to connect: {0}
Problem None.
User response None.
WSWS3518I: Target address: {0} is already connected.
Problem None.
User response None.
WSWS3519I: Disconnecting target address: {0}. Mark the object to be closed: {1}
Problem None.
User response None.
WSWS3520I: Target address: {0} is already disconnected. The connection object: {1} is already marked.
Problem None.
User response None.
WSWS3521I: Reset the connection object for target address: {0}. Connection is persistent? {1}
Problem None.
User response None.
WSWS3522I: Read keystore password property for: {0}
Problem Indicate how many keystore password properties have been identified.
User response None.
WSWS3523E: The serialization engine detected an element nesting greater than 100 elements. This exceeds the limit of the serialization engine. This problem was found while serializing an object of class: {0}
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.
WSWS3524E: The requested WSDL document is not displayed because there are no SOAP ports present in the requested WSDL. Use the /extwsdl query to access the full WSDL document.
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.
WSWS3525E: Exception occurred while loading "META-INF/services/CustomBindingProvider.xml" files.
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.
WSWS3526W: No namespace was found for a mapping defined in the file {0}.
Problem It's expected that every custom type mapping has a non-default namespace.
User response Correct the CustomBindingProvider.xml file.
WSWS3527I: Discovered and loaded the custom binding provider from the file: {0}
Problem None
User response None
WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ---------- Extension base mismatch between existing Bean and WSDL document. Existing Bean class: "{0}" Extends the following class: {1} However the following extension base is specified in the WSDL document: {2}
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.
WSWS3529I: Outbound connection object expired: {0}. Time from the last access to the object: {1} millieseconds.
Problem None.
User response None.
WSWS3530I: Found an existed outbound connection object: {0} in the cache.
Problem None.
User response None.
WSWS3531I: Created a new outbound connection object: {0} in the cache using virtual connection factory: {1}
Problem None.
User response None.
WSWS3532I: Returning a closed outbound connection object: {0} to the cache.
Problem None.
User response None.
WSWS3533I: Returning an outbound connection object: {0} to the cache.
Problem None.
User response None.
WSWS3534W: Encountered unknown outbound connection object: {0}
Problem Runtime found an unknown outbound connection object. It could be an internal error.
User response Check for connection exception in the log.
WSWS3535I: Remove outbound connection object: {0} from the cache.
Problem None.
User response None.
WSWS3536I: New connection established with virtual connection object: {0}
Problem None.
User response None.
WSWS3537I: Connection established already with virtual connection object: {0}
Problem None.
User response None.
WSWS3538W: A connection is attempted with outbound connection object that is already marked to be closed: {0}
Problem Access to a closed connection is attempted. This could be an internal error.
User response Check for connection exception in the log.
WSWS3539E: Exception {0} is caught. Release related virtual connection object:{1} and outbound service context: {2}
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.
WSWS3540I: Key {0} found for connection table lookup: {1}
Problem None.
User response None.
WSWS3541E: Error: Attribute {0} is referenced but not defined.
Problem WSDL2Java error indicating that an attribute is referenced but no definition was found.
User response Please correct your wsdl.
WSWS3542I: Each failed HTTP connection will be retried until succeeds.
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.
WSWS3543I: Number of retries for failed HTTP connection: {0}.
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.
WSWS3544W: Exception caught: {0}. HTTP connection to retry: {1}.
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.
WSWS3545I: Released object: {0}
Problem None.
User response None.
WSWS3546I: Current size of the connection object pool: {0}
Problem None.
User response None.
WSWS3547I: Outbound connection group is created for key: {0}
Problem None.
User response None.
WSWS3548W: Warning: WSDL2Java could not discover a suitable StubWriter. The default SOAP StubWriter will be used.
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/.
WSWS3549E: Error: WSDL2Java could not discover a suitable StubWriter for {0}.
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/.
WSWS3550E: Error: The MessageContext specifies Style {0} but the OperationDesc specifies Style {1}.
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/.
WSWS3551E: Error: The MessageContext specifies Use {0} but the OperationDesc specifies Use {1}.
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/.
WSWS3552E: Error: Can not load the Java class for the custom binder: {0}.
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/.
WSWS3553E: Error: The value of -MIMEstyle must be AXIS, swaRef or WSDL11.
Problem The -MIMEstyle option of Java2WSDL is incorrect.
User response Use a correct -MIMEstyle option.
WSWS3554E: Error: Group {0} is referenced but not defined.
Problem WSDL2Java error indicating that a group is referenced but no definition was found.
User response Please correct your wsdl.
WSWS3555E: Error: AttributeGroup {0} is referenced but not defined.
Problem WSDL2Java error indicating that a attributeGroup is referenced but no definition was found.
User response Please correct your wsdl.
WSWS3556I: No compression will be performed for HTTP Content-Encoding.
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.
WSWS3557I: Compression type of <gzip(x-gzip)> enabled? {0}
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.
WSWS3558I: Compression type of {deflate} enabled? {0}
Problem Indicate whether the compression type of deflate is enabled.
User response Check the Web services property for HTTP compression is configured as needed.
WSWS3559I: Using {0} type of HTTP Channel.
Problem Indicate what type of HTTP Channel is used for HTTP connection. It could be an In-process or network type.
User response None.
WSWS3560W: Unable to get an Inprocess Channel: {0}. Proceed now with a network type of Channel.
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.
WSWS3561E: Mapped to cluster name <{0}> using - host: {1}, port: {2}, URI path: {3}
Problem The printed data was used to map to a valid cluster name.
User response None.
WSWS3562W: Warning: The -wrapped option setting is only useful if -style DOCUMENT and -use LITERAL. Processing continues and the wrapped setting is ignored.
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.
WSWS3563I: Accept-Encoding header from incoming HTTP request = {0}
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.
WSWS3564I: ChannelFramework EndPoint object: {0} is mapped, using Identity object of {1}
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.
WSWS3565E: Error: Invalid endpoint argument to Service.getPort {0}
Problem The specified endpoint was used to invoke Service.getPort.
User response Correct the invocation of Service.getPort.
WSWS3566E: Error: Invalid port for Service.createCall: {0}
Problem The specified port was used to invoke Service.createCall.
User response Correct the invocation of Service.createCall.
WSWS3567E: Error: Invalid operation for Service.createCall: {0}
Problem The specified operation was used to invoke Service.createCall.
User response Correct the invocation of Service.createCall.
WSWS3568E: ---------- WSDL2Java VALIDATION ERROR ---------- Existing Bean class is invalid: "{0}" It does not define a set method for the following data member = {1} A get method was found = {2}
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.
WSWS3569I: Inbound {0} {1} request: Content-Type: {2} Message contents:
Problem The following message was received as a Web services request.
User response None.
WSWS3570I: Inbound {0} {1} response: Content-Type: {2} Message contents:
Problem The following message was received in response to a previous Web services request.
User response None.
WSWS3571I: Outbound {0} {1} request: Content-Type: {2} Message contents:
Problem The following message was sent as a Web services request.
User response None.
WSWS3572I: Outbound {0} {1} response: Content-Type: {2} Message contents:
Problem The following message was sent as a response to a Web services request.
User response None.
WSWS3573E: Cluster identity object: {0} found by the RequestMapper using original endpoint address: {1}. If the identity object is null, transport will proceed to use default channels for connections.
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.
WSWS3574E: ---------- FATAL ERRORS ENCOUNTERED ---------- GENERATION OF ARTIFACTS HAS BEEN SUSPENDED. See messages to follow for more details.
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.
WSWS3575E: Failed to set the protection for the SOAPBody.
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/.
WSWS3576I: Info: Changed java name {0} to {1} for xml construct {2} due to mapping file reference.
Problem The JSR109 mapping file defined a name for the xml construct that is different than the default mapping.
User response none
WSWS3577I: Info: Changed java name {0} to {1} for xml construct {2} due to custom binding designation.
Problem The custom binder defined a name for the xml construct that is different than the default mapping.
User response none
WSWS3578I: Info: Changed java name {0} to {1} for xml construct {2} due to java reflection.
Problem Java reflection indicates that the name of the xml construct that is different than the default mapping.
User response none
WSWS3579I: Info: Introspecting SEI {0}. JavaClass is: {1}
Problem Performing introspection of indicated SEI.
User response none
WSWS3580I: Info: Introspecting class for xml construct {0}. JavaClass is: {1}
Problem Performing introspection of indicated class.
User response none
WSWS3581E: Error: PortType operation has no corresponding binding operation: name = {0}, input name = {1}, output name = {2}
Problem An invalid portType operation was encountered in the wsdl.
User response Please correct the wsdl.
WSWS3582E: The ''{0}'' property is invalid unless -bindingTypes http (or no bindingTypes) is also specified.
Problem When property is specified, the corresponding property must also be specified.
User response Respecify the property using bindningTypes http.
WSWS3583E: The ''{0}'' property is invalid unless -bindingTypes jms is also specified.
Problem When property is specified, the corresponding property must also be specified.
User response Respecify the property using bindningTypes jms.
WSWS3584E: The ''{0}'' property is invalid unless -bindingTypes ejb is also specified.
Problem When propertie is specified, the corresponding property must also be specified.
User response Respecify the property using bindingTypes ejb.
WSWS3585W: Warning: PortType operation has no corresponding binding operation containing the same number of input and output parameter names. name = {0}, input name = {1}, output name = {2}
Problem Inconsistent portType and binding operation were encountered in the wsdl.
User response Make sure wsdl is correct.
WSWS3586I: Invoking method: {0}() of class: {1}
Problem none.
User response none
WSWS3587I: Received Cluster Identity object: {0} from WS-Addressing. If the Identity object is null, transport attempts to map one by the RequestMapper.
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.
WSWS3588I: Could not map an Cluster Identity object: {0} to a valid endpoint. Transport attempts to use default channels for connections.
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.
WSWS3589I: Exception caught: {0} resolving the endpoint. Proceed to next option using RequestMapper.
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.
WSWS3590I: Exception caught: {0} resolving the endpoint. Proceed to next option using default channels.
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.
WSWS3591I: An exception which was defined in the WSDL for the the operation has been thrown by the service endpoint. This may not indicate an error.
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.
WSWS3592E: Error: Could not resolve to an operation. The message contains body elements named ""{0}"", and this matches multiple operations ""{1}"". Debug: {2}
Problem This may be a symptom of an incorrect wsdl.
User response Fix your wsdl to remove ambiguity, or CMSG002
WSWS3593E: Error: Operations {0} and {1} have the same parameters elements in their input request message. Please change the wsdl.
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.
WSWS3594E: Error: Methods {0} and {1} have the same parameters names. A document literal non-wrapped wsdl cannot be produced.
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
WSWS3595I: Current pool size: {0}. Connections-in-use size: {1}. Configured pool size: {2}
Problem This informational message describes the current condition of the outbound HTTP connection pool.
User response No user action is required.
WSWS3596I: Current thread: {0} is going to wait for notification.
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.
WSWS3597I: Current thread: {0} is going to wait {1} milliseconds for notification.
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.
WSWS3598I: Notify the next waiting thread.
Problem None.
User response No user action is required.
WSWS3599I: The current thread: {0} has been notified.
Problem None.
User response No user action is required.
WSWS3600I: The connection wait timed out.
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.
WSWS3601E: An unexpected integrity problem occurred with the connection pool.
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/.
WSWS3602I: Current endpoint: {0}. New endpoint: {1}
Problem None.
User response No user action is required.
WSWS3700E: Error: Non-whitespace character content ({0}) was detected in the {1}. Processing cannot continue.
Problem The indicated construct cannot have mixed character content.
User response Correct the SOAP message.
WSWS3701E: Error: An exception was encountered. Use the wsdeploy command to deploy your application. The exception is {0} {1}
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
WSWS3702E: Error: Could not resolve to an operation. The message contains an element named ""{0}"", but this element does not match any operation of the target port. However, the following operation(s) ({1}) have similar information but are a different style. This difference might indicate that the client sent a {2} message and the server is expecting a {3} message. Debug: {4}
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.
WSWS3703E: Error: The WSDL operation, {2}, contains multiple {1} parameters that are mapped to the same qname: {0}.
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.
WSWS3704W: Warning: Java2WSDL encountered a inner nested class named {0} in the input. Inner classes are not supported. Generation will continue.
Problem The input SEI references a class nested inside another class. This is unsupported.
User response Change the Java structure.
WSWS3705E: ERROR: Document: {0}, imported by a wsdl:import from within: {1}, is neither a schema or a WSDL file.
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.
WSWS3706W: WARNING: NOT WS-I Compliant. Document: {1} is using a wsdl:import to import a schema document: {0} WS-I requires wsdl:imports to import only WSDL documents.
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.
WSWS3707W: WARNING: NOT WS-I Compliant. The wsdl:import namespace attribute= {0} in document= {1}, is a relative URI. WS-I requires wsdl:import namespaces to be absolute.
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".
WSWS3708W: WARNING: NOT WS-I Compliant. The schemaLocation attribute of the xsd:import: {0} does NOT resolve to a document whose root element is a schema.
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.
WSWS3709E: Internal Error: Unsupported content found in web services engine. Content of type {0} was found.
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/.
WSWS3710E: Internal Error: Attempt to change encoding on WebServicesInputSource from {0} to {1}.
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/.
WSWS3711E: Internal Error: WebServicesInputSource internal state error: {0}
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/.
WSWS3712E: Internal Error: Attempt to write empty WebServicesInputSource.
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/.
WSWS3713E: Connection to the remote host {0} failed.Received the following error: {1}
Problem A connection to the remote host was not possible.
User response Check connection and/or errors reported for more details.
WSWS3714W: WARNING: NOT WS-I Compliant. WS-I specifies that XML Schema "{2}" statements only appear in the xsd:schema element of the types section. Document: {0}, is using a non-compliant Schema "{2}" to {2}: {1}
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.
WSWS3715E: FATAL ERROR: The WSDL document: {0} contains a wsdl:import for namespace= {1}, but does not specify a "location" attribute. Add a "location" attribute to the specified wsdl:import element.
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.
WSWS3716W: WARNING: NOT WS-I Compliant. The WSDL document: "{0}" defines a "wsdl:import" element AFTER defining the following element: "{1}" WS-I specifies that "wsdl:import" elements MUST precede all other elements from the WSDL namespace except for "wsdl:documentation".
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.
WSWS3717W: WARNING: NOT WS-I Compliant. The WSDL document: "{0}" defines a "wsdl:types" element AFTER defining the following element: "{1}" WS-I specifies that "wsdl:types" elements MUST precede all other elements from the WSDL namespace except for "wsdl:documentation" and "wsdl:import".
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.
WSWS3718W: WARNING: Null namespace and targetNamespace NOT supported. Document: {0} does not define a 'namespace' attribute when importing: {1}. The file being imported does not define a 'targetNamespace' either. Please make sure, both, the 'namespace' attribute and the 'targetNamespace' of the imported file, are defined and equal in value.
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.
WSWS3719W: WARNING: NOT WS-I Compliant. Document: {0} imports: {1}, with namespace attribute value of: {2} However, {1}, contains a targetNamespace value of: {3} WS-I requires the import namespace attribute and the targetNamespace of the imported document to be equal.
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.
WSWS3720I: Dynamic Work Load Management Client is enabled: {0}
Problem None.
User response No user action is required.
WSWS3721I: Info: {0} is an asynchronous operation indicated by WS-Addressing.
Problem informational message.
User response no action required.
WSWS3722I: Info: {0} is a Request-Response operation.
Problem informational message.
User response no action required.
WSWS3723E: Error: The value stored as the "{0}" property must be of type 'java.util.HashMap',but was found to be of type "{1}".
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.
WSWS3724E: Error: The java.util.HashMap stored as the "{0}" property was empty.
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.
WSWS3725E: Error: The java.util.HashMap stored as the "{0}" property contains a null key.
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.
WSWS3726E: Error: The java.util.HashMap stored as the "{0}" property should contain keys of type "javax.xml.namespace.QName", but a key of type "{1}" was found.
Problem The java.util.HashMap used with implicit SOAP headers contained a key of the incorrect type.
User response Correct the client application code.
WSWS3727E: Error: The java.util.HashMap stored as the "{0}" property contained a null value.
Problem The java.util.HashMap containing request SOAP headers should contain non-null values.
User response Correct the client application code.
WSWS3728E: Error: The java.util.HashMap stored as the "{0}" property contained a value of type "{1}".
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.
WSWS3729E: Error: The java.util.HashMap stored as the "{0}" property should contain null values.
Problem The java.util.HashMap containing response SOAP headers should contain null values.
User response Correct the client application code.
WSWS3730E: Error: SOAP header "{0}" is restricted from client access.
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.
WSWS3731E: Internal Error: the request SOAP header HashMap should have been previously validated.
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/.
Reference topic    

Terms of Use | Feedback

Last updated: Aug 23, 2005 11:22:57 AM EDT
/com.ibm.Websphere.docinfo/.html

© Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)