WSWS

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.
     -R, -retry <argument>
          how many times to re-attempt to load a WSDL-URI, or one of
          it's imported documents after initial attempt times out.
     -g, -genResolver
          generate an absolute-import resolver.
     -u, -useResolver
          specify an absolute-import resolver to use during parsing.
     -d, -deployScope <argument>
          Valid arguments are: "Request", "Session", "Application".
          Adds a "scope" attribute to the ibm-webservices-bnd.xmi file
          when it is created to specify how often to create a new bean.
          Only applicable when role is "develop-server" or "server".
Explanation These are the options to WSDL2Java.
Action 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)
     -T, -properties <option> | <option>=<value>
          specify extended option(s) and any values it may require.
          example: -properties key1=value1;key2;key3=value3
          example: -properties key1=value1 -properties key2
          Alternatively declare this information in a properties file.
     -b, -propertiesFile <argument>
          filename of a properties file that contains a list of extended properties
          Example of file content:
               key1=value1
     -y, -noWrappedArrays
          Disable .NET wrapped array pattern. Generate beans containing arrays.
     -w, -noWrappedOperations
          Disable .NET wrapped operation pattern. Generate request and response beans.
Explanation These are the extended options to WSDL2Java.
Action 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
     -elementFormDefault <qualified | unqualified>
          indicate elementFormDefault usage
     -attributeFormDefault <qualified | unqualified>
          indicate attributeFormDefault usage
     -help
          displays this message
     -helpX
          displays extended options
Explanation These are the options to Java2WSDL.
Action 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:
Explanation These are the extended options to Java2WSDL.
Action These are advanced options that users should not generally use.
WSWS3004W: Warning: The -location was not set, the value "{0}" is used instead.
Explanation The -location option is a required option.
Action Please specify the -location option.
WSWS3005W: Warning: The -server-side option must have an argument that is Bean or EJB. Defaulting to Bean.
Explanation The -server-side option is incorrect.
Action 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.
Explanation The -transport option is incorrect.
Action 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.
Explanation This pre-existing operation has an output element. It is removed.
Action None.
WSWS3008E: Error: The {0} operation of {1} has a fault element. The faults are removed and the operation is changed to one-way.
Explanation This pre-existing operation has a fault element. It is removed.
Action None.
WSWS3009I: Info: Loading Class {0}
Explanation Loading specified class.
Action None.
WSWS3010I: Info: Generating {0} {1}
Explanation Generating indicated construct.
Action None.
WSWS3011E: Invalid destination type "{0}" specified within a JMS endpoint URL.
Explanation A JMS endpoint URL must specify either 'queue' or 'topic' as the destination type.
Action Correct the JMS endpoint URL and re-try.
WSWS3012E: Invalid property "{0}" encountered in JMS endpoint URL.
Explanation A JMS endpoint URL string contained an unrecognized property.
Action 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
Explanation A JMS endpoint URL string must contain the following properties: connectionFactory, destination, targetService. These properties are used to describe the destination queue or topic and target service.
Action Correct the JMS endpoint URL and re-try.
WSWS3014E: Error creating InitialContext: {0}
Explanation An error occurred while trying to create a JNDI InitialContext object.
Action Use the detailed information in the original error message to determine the problem.
WSWS3015E: Caught NamingException: {0}
Explanation The specified error occurred during a JNDI 'lookup' operation.
Action Ensure that the JNDI name is correct.
WSWS3016E: Caught JMSException: {0}
Explanation A JMS operation resulted in the specified JMSException.
Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS3017E: Linked Exception: {0}
Explanation None.
Action None.
WSWS3018E: Caught exception during request processing: {0}
Explanation The specified exception occurred while a request was being processed.
Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS3019E: Caught WebServicesFault: {0}
Explanation The specified WebServicesFault exception occurred.
Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS3020E: Error getting server engine.
Explanation The Web services message-driven bean listener was unable to retrieve a configured server engine during its initialization.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3021E: The required "{0}" property was not present in the inbound JMS request message.
Explanation The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic. This is an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3022E: Unrecognized inbound JMS request message type.
Explanation The Web services JMS listener received a JMS message that was not a TextMessage or a BytesMessage. The JMS listener supports only these two JMS message types.
Action Ensure that the JMS sender uses the correct JMS message type.
WSWS3023E: Two-way requests are not supported for topic destinations.
Explanation A two-way request/response was invoked for a topic destination, but only one-way requests are supported when using a topic.
Action Ensure that any services which use topic destinations contain only one-way operations. This means that within the WSDL file, the operation does not contain an 'output' message.
WSWS3024E: Root part containing SOAP envelope not found. contentId = {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3025E: Error: Could not locate a parameter named {0} for {1}.
Explanation Suspect a bad mapping file supplied to WSDL2Java.
Action Correct your mapping file.
WSWS3026E: Error: The argument of the -voidReturn option must be "oneway" or "twoway".
Explanation The -voidReturn option is incorrect.
Action Please specify the correct option.
WSWS3027E: Error: The {0} SAX event is not supported by SOAP.
Explanation The message is not a legal SOAP message.
Action Contact party that sent this message.
WSWS3028E: Error: A _Helper class was not found for {0}.
Explanation The _Helper class is needed for proper serialization or deserialization. Serialization or deserialization may fail.
Action Ensure that the _Helper class was properly emitted by WSDL2Java and deployed correctly.
WSWS3029W: Warning: The xml construct named {0} cannot be mapped to a java type. The construct will be mapped to javax.xml.soap.SOAPElement.
Explanation Some xml constructs cannot be mapped to java types.
Action The application code will need to use the SOAPElement methods to construct and analyze the data.
WSWS3030E: Error: An internal error occurred while trying to locate the target method. Debug:{0}
Explanation An internal error occurred. Possibly due to an error in the deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3031E: Error: Serialization cannot occur for {0}. There are no registered type mappings.
Explanation The indicated object cannot be serialized.
Action 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}
Explanation Used either a KeyStore/TrustStore pair or a cryptographic token to get a secure socket factory
Action None.
WSWS3033E: Error: Deserialization cannot occur for {0}.
Explanation The indicated type cannot be deserialized.
Action Make sure that a proper deserializer is registered.
WSWS3034E: Error: The OperationDesc for {0} was not matched to a method of {1}. Debug:{2}
Explanation Internal error caused by improper startup code.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3035E: Error: {0}.{1} threw RuntimeException.
Explanation Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original exception.
Action Correct Handler code to eliminate RuntimeException.
WSWS3036I: Replacing response message with SOAP Fault. Original Response Message: {0}
Explanation Handler generated unexpected RuntimeException. JAX-RPC 1.0 (JSR-101) requires that a SOAPFaultException be generated by server. See log for original response message.
Action Correct Handler code to eliminate RuntimeException.
WSWS3037E: Error: Serialization cannot occur for {0}.
Explanation The indicated object cannot be serialized.
Action Make sure that a proper serializer is registered.
WSWS3038E: Error: Deserialization cannot occur for {0}. There are no registered type mappings.
Explanation The indicated type cannot be deserialized.
Action Make sure that a proper deserializer is registered.
WSWS3039E: Error: Resource has been deleted.
Explanation Trying to access a deleted memory managed data source.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3040E: Error: Malformed arrayType value ''{0}''
Explanation The arrayType attribute in the soap message is invalid.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3041E: Error: Bad authentication type (I can only handle "Basic").
Explanation Only Basic authentication is supported with the SimpleServerEngine.
Action You should not be using the SimpleServerEngine.
WSWS3042E: Error: Invalid boolean (found {0}).
Explanation A boolean value in a soap message must be '0', '1', 'true' or 'false'.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3043E: Error: Unexpected characters in a calendar value: {0}
Explanation A calendar value in a soap message was invalid.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3044E: Error: Bad character or insufficient number of characters in hex string.
Explanation A character in a hex string was invalid.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3045E: Error: Invalid date: {0}
Explanation A bad date value was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3046E: Error: Invalid date/time: {0}
Explanation A bad date/time value was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3047E: Error: Cannot deserialize element {1} of bean {0}.
Child element {1} does not belong in namespace {2}.
Most likely, a third party web services platform has sent an incorrect SOAP message.
Explanation The specified bean does not have a property that matches the element. The soap message cannot be deserialized. If the WSDL's schema contains elementFormDefault="qualified", the element should be qualified with a prefix, or should exist in a default namespace. If the schema contains elementFormDefault="unqualified" or completely omits this attribute, the element should not be qualified, and does not have a namespace at all.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3048E: Error: Class ''{0}'' cannot be specified as a Handler class.
Explanation An attempt was made to deploy the indicated class as a Handler class. However it does not extend the Handler class.
Action Correct your deployment information. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
WSWS3049E: Error: A bad Holder class was encountered: {0}
Explanation An attempt was made to use the specified class as a Holder. However the class does not extend the Holder interface.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3050E: Error: Explicit array length is not a valid integer ''{0}''.
Explanation The soap message contains an array that has a non-integer array length. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3051E: Error: No 'name' attribute was specified in an undeployment element.
Explanation This is normally the result of an internal error in the deployment software.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3052E: Error: Bad envelope namespace: {0}
Explanation The envelope element of the soap message has an incorrect namespace. The message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3053E: Error: An attempt was made to construct a Name object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3054E: Error: An attempt was made to construct a NCName object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3055E: Error: An attempt was made to construct a NegativeInteger object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3056E: Error: An attempt was made to construct a NMToken object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3057E: Error: An attempt was made to construct a NonNegativeInteger object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3058E: Error: An attempt was made to construct a NonPositiveInteger object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3059E: Error: Malformed offset attribute ''{0}''.
Explanation The offset attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3060E: Error: Invalid Parameter mode {0}.
Explanation Internal exception of the WSDL2Java emitter.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3061E: Error: Malformed position attribute ''{0}''.
Explanation The position attribute for the indicated array in the soap message is invalid. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3062E: Error: portName should not be null.
Explanation The portName argument to the service.getCalls method must be a recognized port name.
Action Ensure that the argument to the service.getCalls method is appropriate.
WSWS3063E: Error: An attempt was made to construct a PosInteger object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3064E: Error: Cannot handle non-GET, non-POST request.
Explanation SimpleServerEngine does not understand the request.
Action Don't use the SimpleServerEngine.
WSWS3065E: Error: Unrecognized -scope: {0}. Ignoring it.
Explanation The argument of the scope option must be Request, Application, or Session.
Action Use the proper -scope option when invoking WSDL2Java.
WSWS3066E: Error: Expected ''envelope'' but found {0}
Explanation A soap message does not contain an envelope element.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3067E: Error: Invalid time: {0}
Explanation A bad time value was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3068E: Error: Invalid timezone: {0}
Explanation A bad timezone was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3069E: Error: Found languageSpecificType namespace ''{0}'', expected ''{1}''
Explanation A problem has occurred in the deployment software.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3070E: Error: An attempt was made to construct an UnsignedByte object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3071E: Error: An attempt was made to construct an UnsignedShort object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3072E: Error: An attempt was made to construct an UnsignedInt object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3073E: Error: An attempt was made to construct an UnsignedLong object with an invalid string: {0}
Explanation Normally this is caused by an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3074E: Error: Cannot add a second body to a soap envelope.
Explanation This error could be the result of an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3075E: Error: User ''{0}'' not authenticated (unknown user).
Explanation User cannot be authenticated.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3076E: Error: User ''{0}'' not authenticated.
Explanation User cannot be authenticated.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3077E: Error: User ''{0}'' not authorized to ''{1}''
Explanation User is not authorized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3078E: Error: Cannot convert {0} to bytes.
Explanation Internal Error: The soap message cannot be converted into bytes.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3079E: Error: Cannot convert form {0} to String.
Explanation Internal Error: The soap message cannot be converted into a String.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3080E: Error: Could not convert {0} to bean field ''{1}'', type {2}
Explanation The indicated value could not be assigned to the bean field. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3081E: Error: Could not convert value to int.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3082E: Error: Cannot serialize null arrays.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3083E: Error: getURL failed to correctly process URL; protocol not supported.
Explanation Tool option error. See other messages.
Action Fix the URL.
WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize.
Explanation This message normally indicates that the soap message is invalid. The engine was expecting a simple value when it encountered a child element. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3085E: Error: Cannot invoke Call with null namespace URI for method {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3086E: Error: Cannot serialize a {0} with the ArraySerializer.
Explanation The indicated class cannot be serialized with the array serializer.
Action Suspect a problem with the deployment information.
WSWS3087E: Error: Cannot serialize non-Elements with an ElementSerializer.
Explanation The element serializer can only be used to serialize org.w3c.dom.Element objects.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3088E: Error: Cannot serialize a raw object with the SimpleSerializer.
Explanation The SimpleSerializer cannot be used to serialize a non-registered object.
Action Make sure your this class is registered with an appropriate type.
WSWS3089E: Error: Cannot set location URI: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3090E: Error: Unable to tunnel through {0}:{1}. Proxy returns "{2}"
Explanation Can't make the appropriate tunnel.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3091E: Error: Changing admin password.
Explanation Changed passwords on AdminClient.
Action AdminClient is not fully supported.
WSWS3092E: Error: SOAPElement.setAlternateContent called when a child element is present.
Explanation The SAAJ model is being used incorrectly. Please contact the Web services team. if this problem is occurring in the runtime.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3093E: Error: Could not create Call object in AdminClient.
Explanation Internal Error.
Action Don't use AdminClient.
WSWS3094E: Error: WSDDPort couldn't construct provider!
Explanation Internal Error with deployment software.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3095E: Error: Connection closed.
Explanation The connection is closed. The remote service call cannot be made.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3096E: Error: Duplicate file name: {0}.
Hint: you may have mapped two namespaces with elements of the same name to the same package name.
Explanation WSDL2Java issues this message if an different qnames result in the creation of the same java file.
Action Fix your wsdl or use the NStoPkg options to differentiate the classes.
WSWS3097E: Error: Emitter failure. All input parts must be listed in the parameterOrder attribute of {0}
Explanation The parameter order attribute in the wsdl is incorrect.
Action Fix your wsdl.
WSWS3098E: Error: Emitter failure. Cannot find endpoint address in port {0} in service {1}
Explanation The endpoint address cannot be found.
Action Fix your wsdl.
WSWS3099E: Error: Emitter failure. Invalid endpoint address in port {0} in service {1}: {2}
Explanation The endpoint address is invalid.
Action Fix your wsdl.
WSWS3100E: Error: Emitter failure. No binding found for port {0}
Explanation Specify a binding on the service wsdl port.
Action Fix your wsdl
WSWS3101E: Error: Emitter failure. No binding entry found for {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3102E: Error: Emitter failure. No portType entry found for {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3103E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document.
Hint: make sure <port binding=".."> is fully qualified.
Explanation The binding must be defined if referenced.
Action 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.
Explanation The binding must be defined if referenced.
Action 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.
Explanation The portType must be defined if referenced.
Action 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.
Explanation The portType must be defined if referenced.
Action Fix the WSDL.
WSWS3107E: Error: Generic Error.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3108E: Error: Error: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3109E: Error: Error invoking Web service operation: {0}
Explanation Problem occurred invoking remote Web service.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3110E: Error: Error processing ''{0}''
Explanation Admin error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3111E: Error: Error determining if {0} already exists. Will not generate this file.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3112E: Error: Generating WebServicesFault due to missing SOAPAction.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3113E: Error: Cannot add a second header to a soap envelope.
Explanation This error could be the result of an invalid soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3114E: Error: Internal error.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3115E: Error: Configuration file directory ''{0}'' is not readable.
Explanation The specified directory cannot be read.
Action Fix your configuration.
WSWS3116W: Warn: PERFORMANCE ALERT: The following message is re-parsed: {0}
Explanation Non performant serialization encountered.
Action Examine code and make appropriate changes.
WSWS3117E: Error: Invalid container type (expected "ejb", "web", "client" or "none"), defaulting to "none".
Explanation The -container option of WSDL2Java is wrong.
Action Fix the option setting.
WSWS3118E: Error: Invalid role (expected "develop-client", "deploy-client", "develop-server", or "deploy-server"), defaulting to "develop-client".
Explanation The -role option of WSDL2Java is wrong.
Action 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".
Explanation The Web service always runs in a web or ejb container.
Action Fix the options and rerun WSDL2Java.
WSWS3120E: Error: Configuration is missing.
Explanation This is most likely due to a previous error with the Web services deployment descriptor.
Action Review the log for previous errors.
WSWS3121I: Info: {0} is a oneway operation.
Explanation informational message.
Action no action required.
WSWS3122E: Error: Could not find service {0} referenced in URI {1}
Explanation The specified service could not be found.
Action Check the name of the service specified by the client and the deployment of that service on the server.
WSWS3123E: Error: Javaclass {0} specified for handler {1} must implement {2} OR {3}. The handler will be skipped.
Explanation A configuration file (was-webservices.xml) defines a handle javaclass that does not implement the expected interface.
Action Specify javaclass that implements the expected interface.
WSWS3124W: Warning: Invalid -genJava option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Explanation The -genJava option of WSDL2Java is wrong.
Action Correct the option setting.
WSWS3125W: Warning: Invalid -genXML option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Explanation The -genXML option of WSDL2Java is wrong.
Action Correct the option setting.
WSWS3126E: Error: Could not get a secure socket factory from the following SSL Configuration: {0}.
Explanation Could not get a secure socket factory.
Action Correct your SSL configuration.
WSWS3127E: Error: Invalid WSDD element ''{0}'' (wanted ''{1}'').
Explanation Error occurred during deployment. This is probably an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3128E: Error: Could not make envelope from bytes.
Explanation This could possibly due to a deserialization error. Look for other errors.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3129E: Error: Only interfaces may be used for the proxy Class argument of the Service.getPort method.
Explanation The getPort method requires a proxy interface.
Action 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.
Explanation The proxy Class argument must be an interface that extends java.rmi.Remote.
Action Fix the invocation of the getPort method.
WSWS3131E: Error: Must specify a password for AdminClient.
Explanation A password must be supplied.
Action AdminClient is not fully supported.
WSWS3132E: Error: No target service was found.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3133E: Error: Need to specify a user for authorization.
Explanation No user was found to authorize.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3134E: Error: Remote administrator access is not allowed.
Explanation Cannot administer remotely.
Action The Admin class is not fully supported.
WSWS3135E: Error: Body not found.
Explanation A body was expected in the soap envelope, but was not found. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3136E: Error: No deserializer defined for array type {0}
Explanation The array of the indicated component type could not be deserialized.
Action This problem may be due to invalid deployment information.
WSWS3137E: Error: No deserialization context to use in SOAPElement.convertToObject().
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3138E: Error: No custom elements allowed at top level until after the <body> tag.
Explanation The soap message is invalid and cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3139E: Error: No deserializer for {0}
Explanation Normally this is the result of bad client or server deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3140E: Error: Deserializing parameter ''{0}'': could not find deserializer for type {1}
Explanation Nornally this is the result of a bad soap message or invalid server deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3141E: Error: Could not get DOM document: XML was "{0}"
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3142E: Error: Could not find Web services engine.
Explanation Probably an Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3143W: Warning: Expected instance of 'EngineConfiguration' in environment.
Explanation Invalid configuration data.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3144E: Error: Cannot locate handler: {0}
Explanation Internal Error with deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3145E: Error: No HandlerProvider 'handlerClass' option was specified.
Explanation Missing information in deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3146E: Error: No handlers in {0} ''{1}''
Explanation Missing handlers in deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3147E: Error: no {0} header!
Explanation Header missing in soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3148E: Error: Processing instructions are not allowed within SOAP messages.
Explanation The soap message is invalid and cannot be deserialized due to presences of processing instructions.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3149E: Error: {0}: {1} is not a map.
Explanation The object cannot be serialized by the MapSerializer. This is probably the result of an internal deployment error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3150E: Error: No provider type matches QName ''{0}''
Explanation Deployment information is not complete. This is probably the result of an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3151E: Error: No operation name specified.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3152E: Error: Cannot find operation: {0} - none defined
Explanation The WSDL does not define any operations in the portType.
Action This is an internal error or deployment error.
WSWS3153E: Error: Cannot find operation: {0}
Explanation The WDSL binding did not specify the operation.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3154E: Error: No ''{0}'' option was configured for the service ''{1}''
Explanation The indicated option was not found.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3155E: Error: {0} not found as an input part OR an output part.
Explanation The parameter order attribute must reference a message part.
Action Correct the WSDL.
WSWS3156E: Error: Cannot find port: {0}
Explanation The specified port could not be found by Service.getPort.
Action Correct the invocation of Service.getPort.
WSWS3157E: Error: Cannot find portType: {0}
Explanation The deployed wsdl is missing the portType.
Action Correct the deployed wsdl.
WSWS3158E: Error: No request message in MessageContext?
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3159E: Error: No serializer found for class {0} in registry {1}
Explanation Usually this indicates a internal error with the deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3160E: Error: Cannot find service: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3161E: Error: No service has been defined.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3162E: Error: No service object defined for this Call object.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is {0}
Explanation The Web services engine received a request for the specified target service, but the engine configuration did not contain a port with this name.
Action Compare the endpoint location URL that is being used by the client application with the endpoint location URL contained in the corresponding WSDL document. If you are using the HTTP protocol, make sure that the client application is using the correct URL pattern within the endpoint location URL. If you are using the JMS protocol, make sure that your client application is using an endpoint location URL that contains the correct targetService property. Within a JMS-style endpoint location URL, the targetService property should be set to the name of the desired port component.
WSWS3164E: Error: No security provider in MessageContext.
Explanation Make sure a security provider is configured.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3165E: Error: No HTTP SOAPAction property in context.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3166E: Error: No client transport named ''{0}'' found.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3167E: Error: No transport mapping for protocol: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3168E: Error: No mapped schema type for {0}
Explanation The indicated array component type cannot be serialized. Make sure this type is registered.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3169E: Error: Component requires a type attribute.
Explanation The component of the vector cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3170E: Error: Must include type attribute for Handler deployment!
Explanation Missing deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3171E: Error: No type QName for mapping!
Explanation Missing deployment information in the type mapping registry.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3172E: Error: User ''{0}'' not authorized to ''{1}''
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3173E: Error: Did not understand "MustUnderstand" header(s):{0}
Explanation Handler did not understand mustUnderstand headers.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3174E: Error: No value field for RPCParam to use. {0}
Explanation Internal Exception.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3175E: Error: {0} is null.
Explanation Processing cannot continue because the indicated item is null.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3176E: Error: AdminClient did not initialize correctly: 'call' is null!
Explanation Internal Error.
Action AdminClient is not fully supported.
WSWS3177E: Error: Null namespace URI specified.
Explanation Namespace argument must be specified.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3178E: Error: null parent.
Explanation Tried to call SAAJ setParent with a null argument. This may be the result of an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3179E: Error: Null provider type passed to WSDDProvider.
Explanation Missing deployment information. This may be the result of an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3180E: Error: Null response message.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3181E: Error: Odd number of digits in hex string.
Explanation The HexBinary object cannot be constructed.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3182E: Error: Only one Body element allowed in SOAPEnvelope.
Explanation The soap message contains multiple soap bodies inside the envelope. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3183E: Error: Only one Header element allowed in SOAPEnvelope.
Explanation The soap message contains multiple soap headers inside the envelope. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3184E: Error: Number of parameters passed in ({0}) doesn''t match the number of IN/INOUT parameters ({1}) from the addParameter() calls.
Explanation The number of parameters does not match the expected number of parameters.
Action This could be a DII or internal error.
WSWS3185I: Info: Parsing XML file: {0}
Explanation informational message.
Action no action required.
WSWS3186E: Error: Error in parsing: {0}
Explanation Problem occurred deserializing the soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3187E: Error: Processing file {0}
Explanation AdminClient error processing the indicated file.
Action AdminClient is not fully supported.
WSWS3188I: Info: {0} quitting.
Explanation informational message.
Action no action required.
WSWS3189E: Error: Administration service requested to quit, quitting.
Explanation Admin quitting.
Action Admin class is not fully supported.
WSWS3190E: Error: Unable to bind to port {0}. Did not start SimpleServerEngine.
Explanation Internal Error.
Action SimpleServerEngine not fully supported.
WSWS3191I: Info: Configuration file read-only so engine configuration changes will not be saved.
Explanation informational message.
Action no action required.
WSWS3192E: Error: return code: {0}
{1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3193E: Error: Problem with servlet engine /WEB-INF directory
Explanation /WEB-INF may not be accessible.
Action Correct problem with WEB-INF directory.
WSWS3194E: Error: Problem with servlet engine config file: {0}
Explanation config file may not be accessible.
Action Correct problem with servlet engine config file.
WSWS3195W: Warn: Unable to load/create servlet engine config file, attempting internal default (from jar).
Explanation This exception is unexpected. The cause is not immediately known.
Action no action required.
WSWS3196E: Error: Problem with servlet engine config file (loading from jar).
Explanation Configuration error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3197I: Info: {0} starting up on port {1}.
Explanation informational message.
Action no action required.
WSWS3198E: Error: Type/Element attribute on Part ''{0}'' is not set.
Explanation The WSDL part must specify the type or element attribute.
Action Correct the deployed wsdl.
WSWS3199E: Error: Unexpected end of stream.
Explanation Internal Error or problem with input soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3200E: Error: Unknown host - could not verify administrator access.
Explanation Unknown host encountered by Admin tool.
Action The Admin tool is not fully supported.
WSWS3201E: Error: Where {0} looks like:
Explanation Admin tool error.
Action Admin tool is not fully supported.
WSWS3202E: Error: Error processing WSDL document: {0} {1}
Explanation Normally an error with the deployed wsdl detected during service creation.
Action Correct the deployed wsdl.
WSWS3203E: Error: Missing WSDL document in Service.getPort.
Explanation A WSDL document is needed if you want to use Service.getPort.
Action Correct your deployment information.
WSWS3204E: Error: {0} already exists.
Explanation Internal Error in the WSDL2Java SymbolTable.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3205E: Error: Type {0} is referenced but not defined.
Explanation Your wsdl references types or elements that are not defined.
Action Correct your wsdl.
WSWS3206E: Error: Cannot find EJB at JNDI location {0}
Explanation There may be a problem with your JNDI configuration.
Action Correct your JNDI configuration.
WSWS3207E: Error: Cannot create InitialContext.
Explanation An InitialContext was not created.
Action Inspect other errors to determine why InitialContext was not created.
WSWS3208E: Error: The definition of {0} results in a loop.
Explanation Found recursive definition of the indicated type or element.
Action Correct your wsdl.
WSWS3209E: Error: Bad property. The value for {0} should be of type {1}, but it is of type {2}.
Explanation A bad property detected on the Call or MessageContext. This could be caused by an internal error.
Action Fix the property.
WSWS3210E: Error: Null property name specified.
Explanation A bad property was detected. This could be caused by an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3211E: Error: Null property value specified.
Explanation A null property value was specified. This could be caused by an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3212E: Error: Property name {0} not supported.
Explanation An unsupported property is being used.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3213E: Error: Null getter method specified.
Explanation This is normally due to an internal error associated with the serialization engine.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3214E: Error: Null setter method specified.
Explanation This is normally due to an internal error associated with the deserialization engine.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3215E: Error: Null public instance field specified.
Explanation This is normally due to an internal error with the serialization engine.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3216E: Error: Null java class specified in TypeMappingImpl.isRegistered method.
Explanation The isRegistered method requires a non-null java class. This error could be the result of an internal problem.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3217E: Error: Null qualified name specified in TypeMappingImpl.isRegistered method.
Explanation The isRegistered method requires a non-null qname. This error could be the result of an internal problem.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3218E: Error: Null serializer factory specified in the TypeMappingImpl.register method.
Explanation This error normally suggests a problem with the deployment software.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
Explanation The WSDL contains unsupported MIME constructs.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3220E: Error: Error: Empty or missing service name.
Explanation The WSDL service name is wrong.
Action Correct the WSDL.
WSWS3221E: Error: Bean attribute {0} is of type {1}, which is not a simple type.
Explanation Attributes must be simple types.
Action Correct the WSDL.
WSWS3222E: Error: Attribute is of type {0}, which is not a simple type.
Explanation Attributes must be simple types.
Action Correct the WSDL.
WSWS3223E: Error: Exception caught while constructing handler {0}: {1}
Explanation Problem creating JAXRPC Handler.
Action Review reasons for thrown exception.
WSWS3224I: Info: No disk access, using memory only.
Explanation informational message
Action No action required.
WSWS3225E: Error: No DeserializerFactory for {0}
Explanation This normally indicates a problem with the deployed type mapping registry.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3226E: Error: Null FieldDesc specified.
Explanation Internal Exception.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3227E: Error: Exception:
Explanation Used for various exceptions. See other messages.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3228E: Error: Exception: {0}
Explanation Used for various exceptions.. See other messages.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3229E: Error: ConfigurationException:
Explanation Normally indicates an internal error has occurred.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3230E: Error: ParserConfigurationException:
Explanation Indicates that an error has occurred while configuring the xml parser.
Action Correct the parser configuration.
WSWS3231E: Error: SAXException:
Explanation Indicates that a SAX Exception has occurred. Normally the exception is due to a problem configuring the parser.
Action Correct the parser configuration.
WSWS3232E: Error: java.net.UnknownHostException:
Explanation Normally indicates that an internal error has occurred.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3233E: Error: javax.mail.MessagingException:
Explanation Normally indicates a problem with a MIME message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3234E: Error: java.io.IOException:
Explanation Normally an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3235E: Error: java.io.IOException: {0}
Explanation Normally an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3236E: Error: IllegalAccessException:
Explanation Normally an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3237E: Error: IllegalArgumentException:
Explanation This may be issued during overloaded message processing.
Action This exception is unexpected. The cause is not immediately known.
WSWS3238E: Error: IllegalArgumentException: {0}
Explanation This error may occur during overloaded method processing.
Action This exception is unexpected. The cause is not immediately known.
WSWS3239E: Error: InvocationTargetException:
Explanation A problem occurred invoking the indicated target.
Action This exception is unexpected. The cause is not immediately known.
WSWS3240E: Error: InstantiationException:
Explanation This error may indicate a problem with MIME attachments.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3241E: Error: MalformedURLException:
Explanation Malformed URL Exception occurred in the SimpleServerEngine.
Action This exception is unexpected. The cause is not immediately known.
WSWS3242E: Error: WebServicesFault:
Explanation A WebServicesFault has occurred.
Action See other messages for more detailed information.
WSWS3243I: Info: Mapping Exception to WebServicesFault.
Explanation informational message. See other messages for details about why the fault was issued.
Action This exception is unexpected. The cause is not immediately known.
WSWS3244I: Info: Mapping Exception to WebServicesFault: {0}
Explanation informational message. See other messages for details about why the fault was issued.
Action This exception is unexpected. The cause is not immediately known.
WSWS3245E: Error: WSDL2Java emitter timed out attempting to load: {0}. Make sure the specified URL is accessible. If it is, try increasing ''timeout'' and/or ''retry'' default settings in the WSDL2Java emitter.
Explanation Indicates that the WSDL or one of it's imported documents is not accessible.
Action Make sure the WSDL and/or any imported documents are accessible. You can also increase the timeout & retry values through the WSDL2Java options.
WSWS3246E: Error: SOAPFault.addDetail called when a detail is present.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3247E: Error: No target endpoint address has been set on the Stub or Call object.
Explanation An operation has been invoked on a Stub or Call object, but a target endpoint address was not set.
Action Ensure that the target endpoint address has been set on the Stub or Call object prior to invoking the operation.
WSWS3248E: Error: Unsupported attachment type "{0}" only supporting "{1}".
Explanation Indicates that an unsupported attachment type was encountered.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3249E: Error: This attachment implementation accepts only SOAPPart objects as the root part.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.
Explanation Possibly an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3251E: Error: Stream closed.
Explanation Tried to access a closed stream.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3252E: Error: End of stream encountered before final boundary marker.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3253E: Error: maxCached value is bad: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3254E: Error: Reset and mark not supported!
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3255E: Error: input buffer is null.
Explanation Internal Error
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3256E: Error: Offset is negative: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3257E: Error: Length: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3258E: Error: Write beyond buffer.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3259E: Error: Error reading data stream: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3260E: Error: File for data handler does not exist: {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3261E: Error: Error in MIME data stream, start boundary not found, expected: {0}.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3262E: Error: Error in parsing mime data stream: {0}.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3263E: Error: No support for attachments.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3264E: Error: No content.
Explanation Data Handler has no content.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3265E: Error: No engine configuration file - aborting.
Explanation Possibly an internal error.
Action Make sure your engine configuration is correct.
WSWS3266E: Error: The element "{0}" is an attachment with sub elements which is not supported.
Explanation Child elements were not anticipated in the soap message. The soap message cannot be deserialized.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3267E: Error: Error: Missing type resolution for element {2}, in WSDL message part {0} of operation {1}.
Explanation Your WSDL may be bad.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3268E: Error: The soap:operation for binding operation {0} must have a "use" attribute.
Explanation Probably an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3269E: Error: Default type mapping cannot be modified.
Explanation The type mapping cannot be modified after registration has occurred.
Action Please correct your code.
WSWS3270E: Error: Type mapping cannot be modified via delegate.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3271E: Error: Invalid TypeMapping specified: wrong type or null.
Explanation Invalid TypeMapping registration.
Action Please correct your code.
WSWS3272E: Error: Default type mapping from secondary type mapping registry is already in use.
Explanation Cannot change default type mapping after registration.
Action Please correct your code.
WSWS3273E: Error: There is no stub implementation for the interface:
Explanation You cannot call this getPort method because there is no stub implementation of the interface.
Action Please change your code.
WSWS3274E: Error: {0}: {1} is not a vector.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3275E: Error: Invalid parameter mode byte ({0}) passed to getModeAsString().
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3276E: Error: Marking streams not supported.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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}
Explanation This may be a symptom of a Web service deployment problem or an incorrect SOAP request message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3278E: Error: Attempt to set implementation class on a ServiceDesc which has already been configured.
Explanation Internal Exception.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3279E: Error: Unable to create JavaBean of type {0}. Missing default constructor? Error was: {1}.
Explanation Make sure that the JavaBean has a default constructor.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3280E: Error: The value of -soapAction must be DEFAULT, NONE or OPERATION.
Explanation A bad argument was specified for -soapAction.
Action 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.
Explanation Suspect a problem with the Web service deployment, with the soap message, or hot swapping of the service's SoapBindingImpl class.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3282I: Info: Generating {0}.
Explanation Informational message indicating which java classes are generated by WSDL2Java.
Action no action required.
WSWS3283E: Error: The value of -style must be DOCUMENT or RPC.
Explanation The -style option of Java2WSDL is incorrect.
Action Use a correct -style option.
WSWS3284E: Error: Could not find class ''{0}'' for the service.
Explanation Suspect a Web service deployment error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3285E: Error: Could not find class ''{0}'' for the service ''{1}''.
Explanation Suspect a Web service deployment error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3286E: Error: The <class-of-portType> has already been specified as, {0}. It cannot be specified again as {1}.
Explanation Only one class file may be specified for Java2WSDL.
Action Correct your invocation of Java2WSDL.
WSWS3287E: Error: The <class-of-portType> was not specified.
Explanation A class file must be specified for Java2WSDL.
Action Correct your invocation of Java2WSDL.
WSWS3288E: Error: The wsdl URI has already been specified as, {0}. It cannot be specified again as {1}.
Explanation The WSDL file can only be specified once for WSDL2Java.
Action Correct your invocation of WSDL2Java.
WSWS3289E: Error: The wsdl URI was not specified.
Explanation The WSDL URI must be specified for WSDL2Java.
Action Correct your invocation of WSDL2Java.
WSWS3290E: Error: Unrecognized {0}: ''{1}''
Explanation Inappropriate value for the enumeration.
Action 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.
Explanation Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
Action All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
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.
Explanation Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
Action All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
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.
Explanation Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
Action All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
WSWS3294E: Error: The XML Schema type ''{0}'' is not currently supported.
Explanation WSDL2Java does not support this XML Schema type.
Action Correct your wsdl.
WSWS3295E: Error: Message part {0} of operation or fault {1} has no element or type attribute.
Explanation Each message part must have an element or type attribute which locates the schema element/type.
Action Correct your wsdl.
WSWS3296E: Error: The value of {0} for attachment format must be {1};
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3297E: Error: DIME Type length is {0} which exceeds maximum {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3298E: Error: DIME ID length is {0} which exceeds maximum {1}.
Explanation Internal Error
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3299E: Error: Max chunk size "{0}" needs to be greater than one.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3300E: Error: Max chunk size "{0}" exceeds 32 bits.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3301E: Error: Each DIME Stream must be read fully or closed in succession.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3302E: Error: DIME stream data not padded correctly.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3303E: Error: Received "{0}" bytes to read.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3304E: Error: Received "{0}" as an offset.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3305E: Error: Array to read is null.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3306E: Error: Array size of {0} to read {1} at offset {2} is too small.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3307E: Error: End of physical stream detected when more DIME chunks expected.
Explanation Internal Error
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3308E: Error: End of physical stream detected when {0} more bytes expected.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3309E: Error: There are no more DIME chunks expected!
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3310E: Error: DIME header less than {0} bytes.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3311E: Error: DIME version received "{0}" greater than current supported version "{1}".
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3312E: Error: DIME option length "{0}" is greater stream length.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3313E: Error: DIME stream closed during options padding.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3314E: Error: DIME stream closed getting ID length.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3315E: Error: DIME stream closed getting ID padding.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3316E: Error: DIME stream closed getting type.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3317E: Error: DIME stream closed getting type padding.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3318E: Error: DIME stream received bad type "{0}".
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3319E: Error: A holder could not be found or constructed for the OUT parameter {0} of method {1}.
Explanation Suspect a problem with deploying this Web service.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3320E: Error: Illegal argument passed to ParameterDesc.setJavaType. The java type {0} does not match the mode {1}.
Explanation Suspect a problem with deploying this Web service. Probably an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3321E: Error: Invalid normalizedString value.
Explanation The NormalizedString object could not be set due to an invalid value.
Action Correct the normalizedString value.
WSWS3322E: Error: Invalid token value.
Explanation The Token object could not be set due to an invalid value.
Action Correct the token value.
WSWS3323E: Internal Error occurred while build the property descriptors for {0}.
Explanation Internal Error.
Action Make sure the indicate class complies with JAX-RPC.
WSWS3324E: Error: Problems encountered trying to write schema for {0}
Explanation Could not write the schema for the indicated class. This is probably due to an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3325E: Error: Error looking for parameter names in bytecode: input does not appear to be a valid class file.
Explanation You probably specified an invalid class to Java2WSDL.
Action Correct the indicated class.
WSWS3326E: Error: Error looking for parameter names in bytecode: unexpected end of file.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3327E: Error: Error looking for parameter names in bytecode: unexpected bytes in file.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3328E: Error: The class {0} extends non-bean class {1}. An xml schema anyType will be used to define {0} in the wsdl file.
Explanation Java2WSDL error which indicates that the class cannot be converted into an xml schema type. Note that all java class files have mappings to xml schema types. Converting an existing java service into a Web service via Java2WSDL is not guaranteed.
Action All of the java classes that are part of your Web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your Web service.
WSWS3329E: Error: The XML Schema type ''{0}'' is not valid in the Schema version ''{1}''.
Explanation WSDL2Java error.
Action Please correct your wsdl.
WSWS3330I: Info: {0} already exists, WSDL2Java will not overwrite it.
Explanation WSDL2Java informational message.
Action No action required.
WSWS3331E: Error: Invalid gYearMonth: {0}
Explanation Error occurred while constructing a YearMonth object.
Action Use a correct value.
WSWS3332E: Error: Invalid gYear: {0}
Explanation Error occurred while constructing a Year object.
Action Use a correct value.
WSWS3333E: Error: Invalid gMonth: {0}
Explanation Error occurred while constructing a Month object.
Action Use a correct value.
WSWS3334E: Error: Invalid gDay: {0}
Explanation Error occurred while constructing a Day object.
Action Use a correct value.
WSWS3335E: Error: Invalid gMonthDay: {0}
Explanation Error occurred while constructing a MonthDay object.
Action Use a correct value.
WSWS3336E: Error: Invalid duration: must contain a P.
Explanation Error occurred while constructing a Duration object.
Action Use a correct value.
WSWS3337E: Error: Serializer class {0} does not implement SimpleValueSerializer, which is necessary for attributes.
Explanation This serializer cannot be used to serialize attributes.
Action Please correct your deployed type mappings.
WSWS3338E: Error: JIMI is necessary to use java.awt.Image attachments (http://java.sun.com/products/jimi/).
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3339E: Error: javax.xml.transform.Source implementation not supported: {0}.
Explanation An attempt was made to use the SourceDataHandlerSerializer to serialize a non-SourceStream object.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3340E: Error: The OperationDesc for {0} was not synchronized to a method of {1}.
Explanation Internal Error. This error usually indicates that information was missing in the PortDesc/WSDDPort in regards to the definition of the Web service operations. The engine attempts to deduce the missing information, which may result in this particular error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3341E: Error: No service class was found.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3342E: Error: Cannot handle {0}, can only handle JPEG image types.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3343W: Warning: Factory {0} Ignored: missing required method: {1}.
Explanation Correct your factory implementation.
Action This exception is unexpected. The cause is not immediately known.
WSWS3344W: Warning: Factory {0} Ignored: invoke method failed: {1}.
Explanation Invoke method failed.
Action This exception is unexpected. The cause is not immediately known.
WSWS3345E: Error: Unable to locate a valid EngineConfigurationFactory.
Explanation Missing factory implementation.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3346E: Error: Factory {0} Ignored: unable to load/resolve class.
Explanation Cannot load the indicated factory.
Action Make sure that the factory can be loaded.
WSWS3347E: Error: classname attribute is missing.
Explanation WSDD Deployment information is missing. This may be due to an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3348E: Error: qname attribute is missing.
Explanation WSDD Deployment information is missing. This may be due to an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3349E: Error: Element {0} is referenced but not defined.
Explanation WSDL2Java error indicating that an element is referenced but no definition was found.
Action Please correct your wsdl.
WSWS3350E: Error: Missing type or ref attribute for node ''{0}''
Explanation A type or ref attribute is used to reference a type or element.
Action Please correct your wsdl.
WSWS3351E: Error: Unable to deploy typemapping: {0}
Explanation This may be due to a deployment problems.
Action 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).
Explanation Normally this indicates a problem with the missing or incorrect deployment information.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3353E: Error: Method style for message-based service wasn't one we recognized.
Explanation Internal Error. This is an unsupported api.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3354E: Error: Method ''{0}'' does not match any of the valid signatures for message-style service methods.
Explanation Internal Error. This is an unsupported api.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3355E: Error: unmatchedOp=Binding operation has no corresponding portType operation: name = {0}, input name = {1}, output name = {2}
Explanation An invalid binding operation was encountered in the wsdl.
Action Please correct the wsdl.
WSWS3356E: Error: Couldn''t find an appropriate operation for XML QName {0}
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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}
Explanation The SOAP request message received by the service does not match the WSDL definition.
Action Make sure that the SOAP message sent to the service matches the WSDL definition.
WSWS3358E: Error: ERROR: Unable to match binding fault "{0}" from binding {2}, operation "{1}", to a PortType fault.
Explanation The binding fault must have a corresponding portType fault.
Action Please correct the wsdl
WSWS3359E: Error: Fault is missing a name= attribute in operation "{0}", in binding {1}.
Explanation The binding fault must have a name.
Action Please correct the wsdl.
WSWS3360E: Error: ERROR: Missing <soap:fault> element inFault "{0}" in operation "{1}", in binding {2}
Explanation The binding fault must have an appropriate <soap:fault> element.
Action Please correct the wsdl.
WSWS3361E: Error: Found instance data for {0} in the soap:body instead of the soap:header.
Explanation The soap message is incorrect.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3362E: Error: Didn''t find specified return QName {0}
Explanation The response soap message is incorrect.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3363E: Error: The value of the -use option must be LITERAL or ENCODED.
Explanation The -use option of Java2WSDL is incorrect.
Action Correct the -use option.
WSWS3364E: Error: Invalid class provided for -extraClasses option: {0}
Explanation The -extraClasses option of Java2WSDL is incorrect.
Action Correct the -extraClasses option.
WSWS3365E: Error: Cannot invoke a oneway call when the call has a return type.
Explanation A method was encountered that has a return type, but Java2WSDL was invoked in a mode that assumes that the method is one way.
Action Correct the class.
WSWS3366E: Error: The operation must be specified.
Explanation Probably an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3367E: Error: Failure priming the MessageContext object for operation invocation: {0}
Explanation Probably an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3368E: Error: The deserialization event {0} for ({1}) was unexpected in {2}.
Explanation This can be caused by an internal error or a bad input soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3369E: Error: The builder {0} does not have a SOAPElement to build.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3370E: Error: Only one SOAPEnvelope is allowed in a SOAPFactory.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3371E: Error: Cannot invoke addChildElement on a {0} object.
Explanation Cannot add a child SOAPElement to the indicated object.
Action Correct your code.
WSWS3372E: Error: Cannot add a {0} child element to a {1} object.
Explanation Cannot add the indicated child element.
Action Correct your code.
WSWS3373E: Error: Cannot invoke addTextNode on a {0} object.
Explanation Cannot add a Text node to the indicated object.
Action Correct your code.
WSWS3374E: Error: Cannot replace SOAPElement's attributes.
Explanation Cannot call setAttributes after the SOAPElement has attributes.
Action Correct your code.
WSWS3375E: Error: Cannot replace SOAPElement's MappingScope.
Explanation Cannot call setMappingScope after the SOAPElement has a MappingScope.
Action Correct your code.
WSWS3376E: Error: Don''t know how to convert alternate content of class {0}.
Explanation This is an unrecognized alternate content type.
Action Correct your code.
WSWS3377E: Error: Multiple elements have the name ({0}):{1}.
Explanation Expecting only one child element of the given qname.
Action Correct your code.
WSWS3378E: Error: Can't set alternate content on a SOAPElement that already has alternate content.
Explanation An attempt was made to set alternate content on a SOAPElement that already has alternate content.
Action Make sure you remove the existing alternate content before replacing it.
WSWS3379E: Error: Prefix {0} is undefined.
Explanation The indicated prefix does not have a corresponding namespace uri.
Action Correct your code or soap message.
WSWS3380E: Error: An attempt was made to modify a read-only MappingScope.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3381E: Error: Circular loop encountered while processing MappingScope.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3382E: Error: An unqualified namespace cannot have a prefix. Prefix is {0}.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3383E: Error: Illegal use of xmlns prefix encountered: {0}
Explanation The soap message has an illegal xmlns prefix.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3384E: Error: Admin process failed.
Explanation Admin tool failed.
Action The Admin tool is not fully supported.
WSWS3385E: Error: The onStartChild method of {0} did not return a processor.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3386E: Error: Tried to push a null processor.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3387E: Error: An attempt was made to serialize a null object. This should have been handled in the serialize() method.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3388E: Error: Exception generated while rewinding request handlers during fault processing: exception ignored, processing halted.
Explanation An exception was thrown during handler fault processing.
Action Inspect your handlers.
WSWS3389E: Error: JAXRPC Handler Class {0} not found/loaded, ignored.
Explanation The indicated class could not be found and/or loaded.
Action Determine why the class was not found or loaded.
WSWS3390E: Error: Load of class {0} failed unexpectedly.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3391W: Warn: {0}.handleRequest returned false and failed to set response message.
Explanation Warning.
Action This exception is unexpected. The cause is not immediately known.
WSWS3392E: Error: Unexpected: Unable to create response message on behalf of handler.
Explanation Warning.
Action 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.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3394E: Internal Error: attempted to put {0} into pool of {1}.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3395E: Error: {0}.{1} threw RuntimeException.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3396E: Error: Handler {0}: Protected state violation. (JSR 109, Web services for J2EE, Version 1.0, 6.2.2.2).
Explanation Tried to illegally manipulate xml.
Action Correct your handler.
WSWS3397E: Error: JSR-109 requires that Service.getHandlerRegistry() throw an UnsupportedOperationException in a managed container.
Explanation Cannot call this method in a managed container.
Action Correct your handler.
WSWS3398E: Error: JSR-109 requires that Service.getTypeMappingRegistry() throw an UnsupportedOperationException in a managed container.
Explanation Cannot call this method in a managed container.
Action Correct your handler.
WSWS3399E: Error: {0} ''{1}'' didn''t implement ''{2}''.
Explanation Deployment error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3400I: Info: unexpected exception.
Explanation Probably an internal problem.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3401E: Error: RequestMessage missing on MessageContext.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3402E: Error: INTERNAL: ResponseMessage missing on MessageContext.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3403E: Error: Unexpected Life Cycle State: current="{0}", expected="{1}".
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3404E: Error: Unexpected: SubSet({0}, {1}, {2}): acting as empty set.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3405I: Info: Ignoring exception thrown by {0}.
Explanation Informational Message.
Action No action required.
WSWS3406E: Unexpected exception caught while sending reply message: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3407E: Invalid protocol for JMS URL string: {0}
Explanation The protocol for a JMS URL string should be "jms:"
Action Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.
WSWS3408E: A valid URL string can not be formed from the properties contained in the JMSURLParser object.
Linked exception: {0}
Explanation The set of properties currently contained within the JMSURLParser object cannot form a valid JMS-style URL string.
Action Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.
WSWS3409E: Internal Error: Client/Server mode not set for soap port.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3410E: Invalid value specified for the {0} property.
Explanation The value supplied for the specified property was not correct.
Action Make sure that you use the correct value for the specified property.
WSWS3411E: Request timeout exceeded.
Explanation A request did not complete within the specified timeout period.
Action Make sure that your server is active and is able to process requests within the allotted time.
WSWS3412E: A JMS reply message was received which did not correlate with the JMS request message.
Explanation The JMS correlation id in the reply message did not match the JMS message id in the request message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3413E: The JMS reply message was not of the correct JMS message type.
Explanation The JMS reply message should be of type javax.jms.BytesMessage, but it was a different type.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3414E: Style DOCUMENT, Use LITERAL, and Wrapped do not allow operation {0} to be overloaded.
Explanation To allow overloaded operations would cause duplicate xsi types of the same name.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3415E: Buffer size <= 0
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3416E: Stream closed.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3417W: Response set in MessageContext for a one-way message. Reponse will be ignored.
Explanation Runtime set a response message onto the MessageContext for a one-way message.
Action Correct JAXRPC Handler logic.
WSWS3418E: Error: Exception generated during handler fault processing.
Explanation An exception was thrown during handler fault processing.
Action 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.
Explanation It's not allowed to set a value the node as described in the exception.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3420E: Error: Emitter failure. Part {0} of operation {1} must be a type part.
Explanation The binding use is inconsistent with the parts. When the use is literal, parts can be element parts or type parts. When the use is encoded, parts must be type parts.
Action Fix your wsdl.
WSWS3421E: Error: The service interface ''{0}'' does not subclass ''javax.xml.rpc.Service''.
Explanation The specified interface must subclass 'javax.xml.rpc.Service'.
Action Specify an interface that subclasses 'javax.xml.rpc.Service'.
WSWS3422E: Error: Can not instantiate {0}.
Explanation The object can not be instantiated. An exception may have been logged.
Action Contact the provider of the object which cannot be instantiated to determine the cause of the exception. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
WSWS3423E: Error: "javax.xml.soap.write-xml-declaration" property has to be either true or false.
Explanation This property maps to a boolean value
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3424E: Error: List value of type {1}, is not a simple type.
Explanation xsd:list itemTypes must be atomic values.
Action Correct the WSDL.
WSWS3425I: From target realm: {0}.
Explanation informational message.
Action no action required.
WSWS3426I: HTTP Basic Authentication information has been received.
Explanation informational message.
Action no action required.
WSWS3427I: No HTTP Basic Authentication Information has been received.
Explanation Runtime does not receive any HTTP Basic Authentication information from the prompt. Or the loginSource property is not configured.
Action Make sure userid and password are both entered at the prompt. Or read the InfoCenter to configure the loginSource property.
WSWS3428W: Warning: Found an old J2EE 1.3 version of the DD. A new J2EE 1.4 version will be written.
Explanation This is notification that a previous versioned DD file was found where the DD is to be written. And that a new version will be written.
Action If this is unexpected, check your DD versions.
WSWS3429W: Warning: Found old J2EE 1.3 {0} file. This indicates a version mismatch - a new J2EE 1.4 DD will be written.
Explanation This is notification that a previous versioned DD file was found where the DD is to be written. And that a new version will be written.
Action If this is unexpected, check your DD versions.
WSWS3430E: Invalid CharacterEncoding: {0}.
Explanation Expected valid CharacterEncoding for incoming message.
Action Correct CharacterEncoding for incoming message.
WSWS3431E: Error: No Service Endpoint Class found for port {0}.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3432E: Error: Exception thrown while invoking method ''{0}'' against object ''{2}'' of class ''{3}''.
Explanation Examine exception stack trace for more detail.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3433E: Internal Error: No Processor assigned to port {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3434E: Unable to load configuration file
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3435E: Error: Invalid date/time. Received an empty string for a date/time value.
Explanation An invalid empty string date/time value was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3436E: Error: Invalid time: Received an empty string for a time value.
Explanation An invalid empty string time value was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3437E: Error: Invalid date: Received an empty string for a date value.
Explanation An invalid empty string date value was found in a soap message.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3438E: Error: The service locator ''{1}'' does not subclass the service interface ''{0}''.
Explanation The specified service locator must subclass the service interface.
Action 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}.
Explanation The contents of the SOAP body should have been decrypted by web services security.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
Explanation The mapping file is used to describe the java mappings for xml qnames. In this case, the qname is incorrect or not found. The corresponding information in the mapping file is ignored.
Action If this mapping file was created by non-IBM tooling, please contact contact the vendor. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
WSWS3442E: Error: No output for Call.{0}.
Explanation Call.getOutputParams and Call.getOutputValues cannot be called unless there is output. There is no output until a call to invoke returns. On a call to invokeOneWay, there is never output.
Action Call Call.invoke before calling Call.getOutputParams or Call.getOutputValues.
WSWS3443E: Handler {0}: Protected state violation: SOAPPart missing/removed.
Explanation Improper use of JAX-RPC API in handler.
Action Review and correct use of JAX-RPC APIs.
WSWS3444E: Handler {0}: Protected state violation: SOAPMessage missing/removed.
Explanation Improper use of JAX-RPC API in handler.
Action Review and correct use of JAX-RPC APIs.
WSWS3445E: Handler {0}: Protected state violation: Unexpected exception. Review error log for details.
Explanation Improper use of JAX-RPC API in handler.
Action Review and correct use of JAX-RPC APIs.
WSWS3446E: The endpoint address URL is missing.
Explanation A Web services request was made which involves the JMS transport, but the request does not include a valid endpoint address URL.
Action Make sure that the request contains a valid endpoint address URL. If this request was invoked within the Web Services Gateway, make sure the proper configuration has been done.
WSWS3447E: Error: Could not get a secure socket factory with the SSL settings of JSSE.
Explanation Could not get a secure socket factory using the SSL settings of JSSE
Action Verify your JSSE SSL setting if you intend to use JSSE SSL setting for the SSL configuration.
WSWS3448I: Info: HTTP Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
Explanation Configured HTTP proxy information.
Action None.
WSWS3449I: Info: HTTPS Proxy Hostname: {0}, Proxy Port: {1}, Proxy Username: {2}, Proxy Password: {3}
Explanation Configured HTTPS proxy information.
Action None.
WSWS3450I: Info: SSL configuration is from {0}.
Explanation Specified SSL configuration. It can be by a java property file, a SSL configuration alias, or the JSSE SSL settings.
Action None.
WSWS3451I: Info: Response from Proxy for HTTP CONNECT: {0}.
Explanation HTTP response from Proxy for the HTTP CONNECT request
Action None.
WSWS3452E: Internal Error: Attempted to generate code without first parsing WSDL file.
Explanation Attempt has been made to generate the code without first parsing the WSDL file.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3453I: File {0} will NOT be written. Write permission denied by underlying file system.
Explanation WSDL2Java issues this message if a file write attempt was denied by underlying file operating system. Most likely due to WSAD restrictions.
Action None.
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}
Explanation WS-I mandates that the 'style/use' must be the same for 'input/outputs' and 'faults' in any one binding. For more details visit WS-I at: http://www.ws-i.org/
Action Modify your WSDL document to make the 'style/use' settings for 'inputs, outputs' and/or 'faults' consistent.
WSWS3455I: Error: Invalid -javaSearch option argument "{0}". Valid options are "File", "Classpath", or "Both". Defaulting to "File".
Explanation The -javaSearch option of WSDL2Java is wrong.
Action Correct the -javaSearch option setting.
WSWS3456E: Error: The onStartChild method of {0} does not know understand how to process element {1}. Processing cannot continue.
Explanation Internal Error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3457W: Warning: The WSDL2Java emitter has found relative namespace {0} in the WSDL, and cannot transform it to an absolute namespace.
Explanation The wsdl has a relative namespace, such as "/home", and no ancestor absolute namespaces to pre-catenate and make an absolute namespace, such as "http://www.ibm.com/home".
Action Fix the namespaces in the wsdl.
WSWS3458E: ---------- WSDL2Java VALIDATION ERROR ----------
Incompatible return types found at SEI method: "{0}"
     Existing Java return type = {1}
     WSDL defined return type = {2}
Explanation Validation Error. An existing SEI class return type is not compatible with it's WSDL definition.
Action Correct the incompatibility between your existing SEI and WSDL document.
WSWS3459E: ---------- WSDL2Java VALIDATION ERROR ----------
Incompatible parameter types found at SEI method: "{0}"
     Existing Java parameter type = {1}
     WSDL defined parameter type = {2}
Explanation Validation Error. An existing SEI class parameter type is not compatible with it's WSDL definition.
Action Correct the incompatibility between your existing SEI and WSDL document.
WSWS3460E: ---------- WSDL2Java VALIDATION ERROR ----------
Incompatible field types found in Java class: "{0}"
     Existing Java class field type = {1}
     WSDL defined field type = {2}
Explanation Validation Error. An existing Java class field type is not compatible with it's WSDL definition.
Action Correct the incompatibility between your existing Java class and WSDL document.
WSWS3461E: ---------- WSDL2Java VALIDATION ERROR ----------
     Existing Enumeration class is invalid: "{0}"
     Missing the following JAX-RPC required method = {1}
Explanation Validation Error. An existing Enumeration class is missing a required method.
Action Add the specified method to the Enumeration class.
WSWS3462E: ---------- WSDL2Java VALIDATION ERROR ----------
     Existing Enumeration class is invalid: "{0}"
     Contains invalid method = {1}
Explanation Validation Error. An existing Enumeration class contains an invalid method.
Action 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}
Explanation Validation Error. An existing Bean class does not contain required default constructor.
Action Add a default constructor to specified Bean.
WSWS3464E: ---------- WSDL2Java VALIDATION ERROR ----------
     Existing Bean class is invalid: "{0}"
     It extends a non-bean class = {1}
Explanation Validation Error. Specified Bean class does not extend an appropriate Java class.
Action Change the specified bean class to extend a compatible Java class.
WSWS3465E: ---------- WSDL2Java VALIDATION ERROR ----------
     Existing Bean class is invalid: "{0}"
     It does not define a bean property for the following data member = {1}
Explanation Validation Error. Specified Bean does NOT have corresponding bean properties for it's data members.
Action Make the data member public, or add corresponding getters and setters.
WSWS3466E: ---------- WSDL2Java VALIDATION ERROR ----------
     Existing Fault class is invalid: "{0}"
     It does not extend = {1}
Explanation Validation Error. Specified fault class is not a Java Exception class.
Action 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.
Explanation Validation Error. Specified Fault class does not implement a constructor with correct number of parameters.
Action Make sure Fault class implements a public constructor with required parameters.
WSWS3468E: ---------- WSDL2Java VALIDATION ERROR ----------
     Existing Fault class is invalid: "{0}"
     It does not define a property for the following data member = {1}
Explanation Validation Error. Specified Fault class does NOT have corresponding bean properties for it's data members.
Action Make the data member public, or add corresponding getters and setters.
WSWS3469E: ---------- WSDL2Java VALIDATION ERROR ----------
Incompatible parameter types found at Fault class method: "{0}"
     Existing Java parameter type = {1}
     WSDL defined parameter type = {2}
Explanation Validation Error. An existing Fault class parameter type is not compatible with it's WSDL definition.
Action Correct the incompatibility between your existing Fault class and WSDL document.
WSWS3470E: Error while running class ''{0}''.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3471W: Binding {0} has already been generated and will not be re-generated.
Explanation None.
Action 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.
Explanation None.
Action None.
WSWS3473E: No binding generator was found for binding type ''{0}''.
Explanation An unsupported binding type was requested.
Action Ensure that only valid binding types are requested.
WSWS3474I: Found a binding generator for binding type ''{0}''.
Explanation None.
Action None.
WSWS3475W: A binding specific location property was not specified for the requested {0} binding. The default location ''{1}'' will be used.
Explanation None.
Action None.
WSWS3476W: The generic -location option should not be used when more than one binding type has been requested.
Explanation You have requested more than one binding type with the -bindingTypes option, but you have specified a single endpoint location URI with the -location option. When requesting multiple binding types, you should specify binding-specific endpoint location URI values for each of the requested binding types by using the <binding-type>.location properties instead of using the -location command-line option.
Action Specify multiple endpoint location URI values with the -properties option.
WSWS3477I: Binding-specific properties are {0}
Explanation None.
Action None.
WSWS3479E: The ''{0}'' property is required, but was not specified.
Explanation Required property needs to be specified.
Action Specify required property.
WSWS3480E: One or more errors occurred while validating the input properties.
Explanation See previously reported errors.
Action Fix cause of previously reported errors.
WSWS3481E: There is no binding defined for {0} RequestSender.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3482E: There is no deployment descriptor defined for {0} RequestSender.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3483E: Could not find WSDL file ''{0}'' within the EAR.
Explanation WSLD file could not be found where it was expected.
Action Fix the EAR.
WSWS3484E: Caught {0} while trying to read WSDL file ''{1}'': {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3485E: No WSDL services were found for namespace ''{0}''.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3486E: The ClassLoader parameter was passed in as null.
Explanation The ClassLoader parameter is required for the method to function properly, but a null value was passed in.
Action Ensure that a non-null value is passed in for the ClassLoader parameter.
WSWS3487E: The port name and service ref name are both null.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3488E: Error: This SOAPElement is not a swaRef - it is not a reference to an attachment.
Explanation Either this SOAPElement does not contain a text node, or the text node does not refer to an attachment.
Action Make sure this is a swaRef element by calling isSwaRef.
WSWS3489E: Error: Mime type {0} does not match object type {1}.
Explanation The mimeType must be consistent with the object: image/gif, image/jpeg ==> java.awt.Image text/plain ==> java.lang.String multipart/* ==> javax.mail.internet.MimeMultipart text/xml, application/xml ==> javax.xml.transform.Source (actually, javax.xml.transform.stream.StreamSource) all others ==> javax.activation.DataHandler
Action Make sure the parameters to addSwaRefTextNode are consistent.
WSWS3490E: Error: The system cannot load the file referenced within {0}. The problem is with {1}.
Explanation File specified by user was not found in the file system.
Action Make sure file exists and/or that it was spelled correctly.
WSWS3491E: Error: Reading import file: {0}
Explanation Import ile specified by in wsdl was not found in the file system.
Action Make sure file exists and/or that it was spelled correctly.
WSWS3492W: Warning: Invalid option combination: style={0} and use={1}
           Will default to document/literal.
Explanation document/encoded is an invalid combination of style/use.
Action Use a valid combination of style/use: rpc/encoded rpc/literal document/literal
WSWS3493E: Error: Invalid combination: style="{0}" and use="{1}"
For binding="{2}" and binding operation="{3}"
Explanation document/encoded is an invalid combination of style/use.
Action 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.
Explanation Configured syncTimeout value in seconds.
Action None.
WSWS3495I: {0} is used as the final endpoint address.
Explanation None.
Action None.
WSWS3496I: {0} is used as the proxy address.
Explanation None.
Action None.
WSWS3497I: Status in the HTTP response: {0}, {1}
Explanation Inform the HTTP response from the server.
Action None.
WSWS3498E: No HTTP status has been received for the current HTTP response.
Explanation No HTTP status information is available to determine the HTTP response.
Action Make sure the target HTTP server is up.
WSWS3499W: Redirected new location: {0}
Explanation Received HTTP response indicates a new location for the target resource.
Action User may want to check WebSphere InfoCenter for details about how to accept the automatic redirection to the new location.
WSWS3500I: Required service: {0} from JNDI namespace: {1}
Explanation None.
Action None.
WSWS3501E: Failures from the Channel Framework service: {0}
Explanation There are failures from the Channel Framework service.
Action Check errors reported by Channel Framework service in the log.
WSWS3502E: Unsupported schema for HTTP: {0}
Explanation Found unsupported schema for using HTTP transport.
Action Verify the target endpoint address.
WSWS3503I: Updated configuration of the outbound connection for key: {0}
Explanation None.
Action None.
WSWS3504E: Failed to retrieve HTTP(S) proxy information for the proxy connection.
Explanation Runtime failed to get the HTTP proxy information to process the proxy connection.
Action Make sure the HTTP or HTTPS proxy information is configured properly. User may want to check WebSphere InfoCenter about how to configure for HTTP proxy.
WSWS3505I: Creating channel named: {0}
Explanation None.
Action None.
WSWS3506I: Found channel named: {0}
Explanation None.
Action None.
WSWS3507I: Creating channel chain named: {0}
Explanation None.
Action None.
WSWS3508I: Found channel chain named: {0}
Explanation None.
Action None.
WSWS3509I: Expect 100 Continue in the HTTP response...sending HTTP request headers only to connection: {0}
Explanation The Expect 100-Continue header is set. Only HTTP request headers are sent to determine if server is willing to accept the HTTP request.
Action None.
WSWS3510I: Sending both HTTP request headers and body message to connection: {0}
Explanation None.
Action None.
WSWS3511I: Sending current request to {0} in version: {1}
Explanation Sending current SOAP over HTTP request in indicated HTTP version.
Action None.
WSWS3512E: Unsupported HTTP version: {0}
Explanation Unsupported HTTP version is detected. This is an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3513E: Invalid HTTP response received from the connection for: {0}
Explanation Invalid HTTP response is received. This could be an internal error.
Action None.
WSWS3514E: No HTTP response body is available from the connection for: {0}
Explanation There are failures with the HTTP Channel service.
Action Check errors reported by HTTP Channel service in the log.
WSWS3515E: Failures with the SSL Channel services: {0}
Explanation There are failures with the SSL Channel service.
Action Check errors reported by SSL Channel service in the log.
WSWS3516I: Received cookie for HTTP header: {0} in the response from connection to: {1}
Explanation None.
Action None.
WSWS3517I: Target address to connect: {0}
Explanation None.
Action None.
WSWS3518I: Target address: {0} is already connected.
Explanation None.
Action None.
WSWS3519I: Disconnecting target address: {0}. Mark the object to be closed: {1}
Explanation None.
Action None.
WSWS3520I: Target address: {0} is already disconnected. The connection object: {1} is already marked.
Explanation None.
Action None.
WSWS3521I: Reset the connection object for target address: {0}. Connection is persistent? {1}
Explanation None.
Action None.
WSWS3522I: Read keystore password property for: {0}
Explanation Indicate how many keystore password properties have been identified.
Action 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}
Explanation An attempt was made to serialize a message with too deep a nesting. This could be due to a linked list with too many nodes. This problem could also be due to an attempt to serialize a graph containing looped references.
Action Please correct the data being serialized.
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.
Explanation Appending "/wsdl" to a service URL is a request to retrieve a WSDL document that contains SOAP ports for the HTTP or JMS transports. If there are no such ports, this error is displayed instead of the WSDL document.
Action Modify the query to obtain the extended wsdl or contact the Web service owner.
WSWS3525E: Exception occurred while loading "META-INF/services/CustomBindingProvider.xml" files.
Explanation The engine or tool failed to parse the CustomBindingProvider.xml to build the CustomProvider object.
Action Check the CustomBindingProvider.xml files to see whether there are any syntax error.
WSWS3526W: No namespace was found for a mapping defined in the file {0}.
Explanation It's expected that every custom type mapping has a non-default namespace.
Action Correct the CustomBindingProvider.xml file.
WSWS3527I: Discovered and loaded the custom binding provider from the file: {0}
Explanation None
Action 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}
Explanation Validation Error. Specified Bean class does not extend same extension base specified in WSDL document.
Action Change the specified Bean class or WSDL document to extend appropriate Java class.
WSWS3529I: Outbound connection object expired: {0}. Time from the last access to the object: {1} millieseconds.
Explanation None.
Action None.
WSWS3530I: Found an existed outbound connection object: {0} in the cache.
Explanation None.
Action None.
WSWS3531I: Created a new outbound connection object: {0} in the cache using virtual connection factory: {1}
Explanation None.
Action None.
WSWS3532I: Returning a closed outbound connection object: {0} to the cache.
Explanation None.
Action None.
WSWS3533I: Returning an outbound connection object: {0} to the cache.
Explanation None.
Action None.
WSWS3534W: Encountered unknown outbound connection object: {0}
Explanation Runtime found an unknown outbound connection object. It could be an internal error.
Action Check for connection exception in the log.
WSWS3535I: Remove outbound connection object: {0} from the cache.
Explanation None.
Action None.
WSWS3536I: New connection established with virtual connection object: {0}
Explanation None.
Action None.
WSWS3537I: Connection established already with virtual connection object: {0}
Explanation None.
Action None.
WSWS3538W: A connection is attempted with outbound connection object that is already marked to be closed: {0}
Explanation Access to a closed connection is attempted. This could be an internal error.
Action Check for connection exception in the log.
WSWS3539E: Exception {0} is caught. Release related virtual connection object:{1} and outbound service context: {2}
Explanation An exception has caused the release of saved virtual connection object and outbound service context.
Action Check from the log for the previous exception caught.
WSWS3540I: Key {0} found for connection table lookup: {1}
Explanation None.
Action None.
WSWS3541E: Error: Attribute {0} is referenced but not defined.
Explanation WSDL2Java error indicating that an attribute is referenced but no definition was found.
Action Please correct your wsdl.
WSWS3542I: Each failed HTTP connection will be retried until succeeds.
Explanation Based on a Java system property setting, each HTTP connection will be retried until the connection succeeds. However, this is not recommended as deadlock may happen.
Action User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections.
WSWS3543I: Number of retries for failed HTTP connection: {0}.
Explanation Based on a Java system property setting, each HTTP connection will be retried for the configured number of times. However, user needs to be cautious about changing this property as deadlock may sometimes happen. Default value is 3.
Action User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections.
WSWS3544W: Exception caught: {0}. HTTP connection to retry: {1}.
Explanation The reported exception is caught, but the HTTP connection will be retried until the configured number of times is reached.
Action User should consider to modify the configuration of the target's HTTP inbound transport to accept more connections.
WSWS3545I: Released object: {0}
Explanation None.
Action None.
WSWS3546I: Current size of the connection object pool: {0}
Explanation None.
Action None.
WSWS3547I: Outbound connection group is created for key: {0}
Explanation None.
Action None.
WSWS3548W: Warning: WSDL2Java could not discover a suitable StubWriter. The default SOAP StubWriter will be used.
Explanation Internal discovery problem, perhaps with classloader.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3549E: Error: WSDL2Java could not discover a suitable StubWriter for {0}.
Explanation Internal discovery problem, perhaps with classloader. Can't continue.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3550E: Error: The MessageContext specifies Style {0} but the OperationDesc specifies Style {1}.
Explanation A bad property detected on the MessageContext or OperationDesc. This could be caused by an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3551E: Error: The MessageContext specifies Use {0} but the OperationDesc specifies Use {1}.
Explanation A bad property detected on the MessageContext or OperationDesc. This could be caused by an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3552E: Error: Can not load the Java class for the custom binder: {0}.
Explanation Either the above custom binder does not exist or it is not in the classpath for the context classloader.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3553E: Error: The value of -MIMEstyle must be AXIS, swaRef or WSDL11.
Explanation The -MIMEstyle option of Java2WSDL is incorrect.
Action Use a correct -MIMEstyle option.
WSWS3554E: Error: Group {0} is referenced but not defined.
Explanation WSDL2Java error indicating that a group is referenced but no definition was found.
Action Please correct your wsdl.
WSWS3555E: Error: AttributeGroup {0} is referenced but not defined.
Explanation WSDL2Java error indicating that a attributeGroup is referenced but no definition was found.
Action Please correct your wsdl.
WSWS3556I: No compression will be performed for HTTP Content-Encoding.
Explanation There will be no compression performed for the HTTP content encoding in the HTTP request or the HTTP response. Hence, the Web services property for HTTP compression has been ignored.
Action User can consider the followings: 1.) validate the value of Web services property for HTTP compression, 2.) check for error messages from HTTP Channel, or 3.) do nothing if compression is not needed.
WSWS3557I: Compression type of <gzip(x-gzip)> enabled? {0}
Explanation Indicate whether the described compression type are enabled. Note that gzip and x-gzip use the same compression mechanism.
Action Check the Web services property for HTTP compression is configured as needed.
WSWS3558I: Compression type of <deflate> enabled? {0}
Explanation Indicate whether the compression type of deflate is enabled.
Action Check the Web services property for HTTP compression is configured as needed.
WSWS3559I: Using {0} type of HTTP Channel.
Explanation Indicate what type of HTTP Channel is used for HTTP connection. It could be an In-process or network type.
Action None.
WSWS3560W: Unable to get an Inprocess Channel: {0}. Proceed now with a network type of Channel.
Explanation There might be an error when the system attempted to find an Inprocess HTTP Channel. However, this may not be a problem unless an in-process connection is required. The system will proceed with a network type of Channel instead.
Action If necessary, check the trace for Work Load Management(WLM) or Dynamic Work Load Management Client(DWLMclient) errors.
WSWS3561E: Mapped to cluster name <{0}> using - host: {1}, port: {2}, URI path: {3}
Explanation The printed data was used to map to a valid cluster name.
Action None.
WSWS3562W: Warning: The -wrapped option setting is only useful if -style DOCUMENT and -use LITERAL. Processing continues and the wrapped setting is ignored.
Explanation The -wrapped option is only applicable if -use LITERAL and -style DOCUMENT.
Action Remove the -wrapped option or set the -use/-style options correctly.
WSWS3563I: Accept-Encoding header from incoming HTTP request = {0}
Explanation This indicates the value set by the web services client for acceptable content-codings in the HTTP response. Please refer to the specification of Hypertext Transfer Protocol for further details. Header value of null indicates empty Accept-Encoding header in the incoming HTTP request;hence, no content encoding is done in the HTTP response.
Action If it is a WebSphere Web services client, check the Web services property for Http compression encoding of the target service port. Make sure the value is configured properly.
WSWS3564I: ChannelFramework EndPoint object: {0} is mapped, using Identity object of {1}
Explanation This printed data was used to map for a channelframework endpoint object that can be used later to create In-process connection.
Action None.
WSWS3565E: Error: Invalid endpoint argument to Service.getPort {0}
Explanation The specified endpoint was used to invoke Service.getPort.
Action Correct the invocation of Service.getPort.
WSWS3566E: Error: Invalid port for Service.createCall: {0}
Explanation The specified port was used to invoke Service.createCall.
Action Correct the invocation of Service.createCall.
WSWS3567E: Error: Invalid operation for Service.createCall: {0}
Explanation The specified operation was used to invoke Service.createCall.
Action 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}
Explanation Validation Error. Specified Bean does not correctly define a bean property for the designated data member.
Action Make the data member public, or add an appropriate setter method. Be particularly careful to ensure that the get and set methods use the same capitalization.
WSWS3569I: Inbound {0} {1} request:
Content-Type: {2}
Message contents:

Explanation The following message was received as a Web services request.
Action None.
WSWS3570I: Inbound {0} {1} response:
Content-Type: {2}
Message contents:

Explanation The following message was received in response to a previous Web services request.
Action None.
WSWS3571I: Outbound {0} {1} request:
Content-Type: {2}
Message contents:

Explanation The following message was sent as a Web services request.
Action None.
WSWS3572I: Outbound {0} {1} response:
Content-Type: {2}
Message contents:

Explanation The following message was sent as a response to a Web services request.
Action 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.
Explanation The RequestMapper of Dynamic Work Load Management Client may have or have not found a matching cluster identity. If the object is null, transport will proceed to use default channels for connections.
Action If Clustering is used, check for errors from Dynamic Work Load Management Client(DWLMClient) in trace.
WSWS3574E: ---------- FATAL ERRORS ENCOUNTERED ----------
     GENERATION OF ARTIFACTS HAS BEEN SUSPENDED.
     See messages to follow for more details.
Explanation Fatal errors have been encountered most likely due to user error. More details in messages to follow. Code/Artifacts generation has been suspended.
Action Correct problems reported and try again.
WSWS3575E: Failed to set the protection for the SOAPBody.
Explanation Attempted to protect the SOAP message body befor invoking the JAX-RPC handlers, however, an unknown error occurred while doing so.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3576I: Info: Changed java name {0} to {1} for xml construct {2} due to mapping file reference.
Explanation The JSR109 mapping file defined a name for the xml construct that is different than the default mapping.
Action none
WSWS3577I: Info: Changed java name {0} to {1} for xml construct {2} due to custom binding designation.
Explanation The custom binder defined a name for the xml construct that is different than the default mapping.
Action none
WSWS3578I: Info: Changed java name {0} to {1} for xml construct {2} due to java reflection.
Explanation Java reflection indicates that the name of the xml construct that is different than the default mapping.
Action none
WSWS3579I: Info: Introspecting SEI {0}. JavaClass is: {1}
Explanation Performing introspection of indicated SEI.
Action none
WSWS3580I: Info: Introspecting class for xml construct {0}. JavaClass is: {1}
Explanation Performing introspection of indicated class.
Action none
WSWS3581E: Error: PortType operation has no corresponding binding operation:
name = {0}, input name = {1}, output name = {2}
Explanation An invalid portType operation was encountered in the wsdl.
Action Please correct the wsdl.
WSWS3582E: The ''{0}'' property is invalid unless -bindingTypes http (or no bindingTypes) is also specified.
Explanation When property is specified, the corresponding property must also be specified.
Action Respecify the property using bindningTypes http.
WSWS3583E: The ''{0}'' property is invalid unless -bindingTypes jms is also specified.
Explanation When property is specified, the corresponding property must also be specified.
Action Respecify the property using bindningTypes jms.
WSWS3584E: The ''{0}'' property is invalid unless -bindingTypes ejb is also specified.
Explanation When propertie is specified, the corresponding property must also be specified.
Action 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}
Explanation Inconsistent portType and binding operation were encountered in the wsdl.
Action Make sure wsdl is correct.
WSWS3586I: Invoking method: {0}() of class: {1}
Explanation none.
Action none
WSWS3587I: Received Cluster Identity object: {0} from WS-Addressing. If the Identity object is null, transport attempts to map one by the RequestMapper.
Explanation The indicated Identity object has been received from WS-Addressing. If null, transport will attempt to map one by the RequestMapper.
Action If clustering is used, check for errors from WS-Addressing in the trace.
WSWS3588I: Could not map an Cluster Identity object: {0} to a valid endpoint. Transport attempts to use default channels for connections.
Explanation The indicated Identity object cannot be mapped to a valid endpoint.
Action If null, check for errors from Clustering and ChannelFramework in the trace.
WSWS3589I: Exception caught: {0} resolving the endpoint. Proceed to next option using RequestMapper.
Explanation An exception was caught. However, the exception can be benign since transport can proceed to next option using the RequestMapper to resolve the endpoint.
Action If applicable, check for errors related to WS-Addressing.
WSWS3590I: Exception caught: {0} resolving the endpoint. Proceed to next option using default channels.
Explanation An exception was caught. However, the exception can be benign since transport can proceed to next option using the default channels to resolve the endpoint.
Action If applicable, check for errors related to Dynamic Work Load Management Client.
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.
Explanation The service endpoint implementation has thrown an exception. This may or may not indicate an error in the service endpoint implementation.
Action Contact the owner of the service endpoint implementation to determine if this exception indicates normal processing or an error condition.
WSWS3592E: Error: Could not resolve to an operation. The message contains body elements named ""{0}"", and this matches multiple operations ""{1}"". Debug: {2}
Explanation This may be a symptom of an incorrect wsdl.
Action 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.
Explanation Document/Literal operations must have unique parameter elements in their input message so that the target server can determine which operation is invoked.
Action Fix your wsdl to remove ambiguity.
WSWS3594E: Error: Methods {0} and {1} have the same parameters names. A document literal non-wrapped wsdl cannot be produced.
Explanation Document/Literal operations must have unique parameter elements in their input message so that the target service can determine which operation is invoked.
Action Specify the -wrapped true option
WSWS3595I: Current pool size: {0}. Connections-in-use size: {1}. Configured pool size: {2}
Explanation This informational message describes the current condition of the outbound HTTP connection pool.
Action No user action is required.
WSWS3596I: Current thread: {0} is going to wait for notification.
Explanation Indicates that the connection pool is full and that the current thread is waiting for openings. The run time might wait for a very long time if the network is busy.
Action If the wait is too long, consider specifying a connection wait timeout, or increase the number of maximum connections, or both. Check for network problems.
WSWS3597I: Current thread: {0} is going to wait {1} milliseconds for notification.
Explanation Indicates that the connection pool is full and that the current thread is waiting for openings for the specified amount of time. If no opening is available, a "Connection timed out" exception might result.
Action If the exception is found,consider increasing the maximum connections value for the connection pool, and the connection wait timeout value to wait for openings in the pool. Check for network problems.
WSWS3598I: Notify the next waiting thread.
Explanation None.
Action No user action is required.
WSWS3599I: The current thread: {0} has been notified.
Explanation None.
Action No user action is required.
WSWS3600I: The connection wait timed out.
Explanation This message is seen with a WebServicesFault exception. The connection wait for an opening in the connection pool has been reached and no connection object is available.
Action Consider increasing the connection wait timeout, and increasing the maximum connections value.Check for network problems.
WSWS3601E: An unexpected integrity problem occurred with the connection pool.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3602I: Current endpoint: {0}. New endpoint: {1}
Explanation None.
Action No user action is required.
WSWS3700E: Error: Non-whitespace character content ({0}) was detected in the {1}. Processing cannot continue.
Explanation The indicated construct cannot have mixed character content.
Action Correct the SOAP message.
WSWS3701E: Error: An exception was encountered. Use the wsdeploy command to deploy your application. The exception is {0} {1}
Explanation An unexpected exception occurred, and the run time has detected generated code from a different build.
Action Deploy your application again with the wsdeploy command. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
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}
Explanation It is possible that the client and the server have different operation styles. This symptom can indicate a Web service deployment problem or an incorrect SOAP request message.
Action Correct the client message so that it matches the style that is expected on the server.
WSWS3703E: Error: The WSDL operation, {2}, contains multiple {1} parameters that are mapped to the same qname: {0}.
Explanation The parameters in the SOAP message must be unique.
Action Change the WSDL message part name and the element attributes to ensure unique parameters.
WSWS3704W: Warning: Java2WSDL encountered a inner nested class named {0} in the input. Inner classes are not supported. Generation will continue.
Explanation The input SEI references a class nested inside another class. This is unsupported.
Action Change the Java structure.
WSWS3705E: ERROR: Document: {0}, imported by a wsdl:import from within: {1},
is neither a schema or a WSDL file.
Explanation Found a non WSDL or schema document being referenced through a wsdl:import.
Action Make sure the document being imported is a valid WSDL document. WSDL:importsimporting a schema is allowed but not recommended.
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.
Explanation Found that a wsdl:import is being used to import a schema document instead of a WSDL file.
Action To be WS-I compliant you must make sure wsdl:imports only import WSDL documents, and that xsd:imports are used instead to import schemas.
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.
Explanation Found that a wsdl:import namespace attribute contains a relative URI. This is not WS-I compliant.
Action To be WS-I compliant you must make the namespace attribute an absolute URI, such as "http://www.ibm.com/home".
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.
Explanation The schemaLocation attribute of the xsd:import does NOT resolve to a document whose root element is a schema. This is not WS-I compliant.
Action To be WS-I compliant you must make sure the schemaLocation attribute resolves to a documet whose root element is a schema.
WSWS3709E: Internal Error: Unsupported content found in web services engine. Content of type {0} was found.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3710E: Internal Error: Attempt to change encoding on WebServicesInputSource from {0} to {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3711E: Internal Error: WebServicesInputSource internal state error: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3712E: Internal Error: Attempt to write empty WebServicesInputSource.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3713E: Connection to the remote host {0} failed.Received the following error: {1}
Explanation A connection to the remote host was not possible.
Action 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}
Explanation A Schema import, include or redefine is not being defined within an xsd:schema element. This is not WS-I compliant.
Action To be WS-I compliant make sure schemas are being imported/included/redefined from within schema elements. Use WSDL "imports" from within a WSDL definition document.
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.
Explanation A wsdl:import statement is missing the 'location' attribute. Processing can not go on.
Action Add the 'location' attribute to the specified wsdl:import element.
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".
Explanation The specified WSDL document is not WS-I compliant as it does not preserve element order specified by WS-I. WS-I specifies that wsdl:import elements MUST precede all other elements from the WSDL namespace except wsdl:documentation.
Action To be WS-I compliant change the order of the wsdl elements defined, and make sure wsdl:imports are only preceded by wsdl:documentation, wsdl:#comment and/or wsdl:#text.
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".
Explanation The specified WSDL document is not WS-I compliant as it does not preserve element order specified by WS-I. WS-I specifies that wsdl:types elements MUST precede all other elements from the WSDL namespace except wsdl:documentation and wsdl:import.
Action To be WS-I compliant change the order of the wsdl elements defined, and make sure wsdl:types are only preceded by wsdl:documentation, wsdl:#comment, wsdl:#text and/or wsdl:import.
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.
Explanation The 'namespace' attribute of the wsdl or xsd import has not been defined and the file being imported does not contain a 'targetNamespace'. This is not a supported configuration.
Action Make sure both, the 'namespace' attribute and the 'targetNamespace' of the imported file, are defined and equal in value.
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.
Explanation WS-I requires import namespace attributes to equal the value of the imported document's targetNamespace.
Action Make sure both, the 'namespace' attribute and the 'targetNamespace' of the imported file, are defined and equal in value.
WSWS3720I: Dynamic Work Load Management Client is enabled: {0}
Explanation None.
Action No user action is required.
WSWS3721I: Info: {0} is an asynchronous operation indicated by WS-Addressing.
Explanation informational message.
Action no action required.
WSWS3722I: Info: {0} is a Request-Response operation.
Explanation informational message.
Action 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}".
Explanation To set implicit SOAP headers on a Stub or Call object, you must use a java.util.HashMap.
Action Correct the client application code.
WSWS3724E: Error: The java.util.HashMap stored as the "{0}" property was empty.
Explanation To set implicit SOAP headers on a Stub or Call object, you must use a non-empty java.util.HashMap.
Action Correct the client application code.
WSWS3725E: Error: The java.util.HashMap stored as the "{0}" property contains a null key.
Explanation The java.util.HashMap used with implicit SOAP headers should contain a non-null key of type "javax.xml.namespace.QName".
Action Correct the client application code.
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.
Explanation The java.util.HashMap used with implicit SOAP headers contained a key of the incorrect type.
Action Correct the client application code.
WSWS3727E: Error: The java.util.HashMap stored as the "{0}" property contained a null value.
Explanation The java.util.HashMap containing request SOAP headers should contain non-null values.
Action Correct the client application code.
WSWS3728E: Error: The java.util.HashMap stored as the "{0}" property contained a value of type "{1}".
Explanation The java.util.HashMap containing request SOAP headers should contain values of type "java.lang.String" or "javax.xml.soap.SOAPElement".
Action Correct the client application code.
WSWS3729E: Error: The java.util.HashMap stored as the "{0}" property should contain null values.
Explanation The java.util.HashMap containing response SOAP headers should contain null values.
Action Correct the client application code.
WSWS3730E: Error: SOAP header "{0}" is restricted from client access.
Explanation The client application attempted to set or get an implicit SOAP header that has been declared as protected.
Action Do not attempt to set or get a protected SOAP header.
WSWS3731E: Internal Error: the request SOAP header HashMap should have been previously validated.
Explanation A validation error was found in the request SOAP header HashMap, yet the HashMap should have been validated previously. This is an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS3732E: Error: This DOM 3 API, method {0} of interface {1}, is not supported.
Explanation This operation is not supported by SAAJ 1.2.
Action Please use a DOM 2 API.
WSWS3733W: Warning: The -deployScope option is ignored unless the -role option is "develop-server" or "server".
Explanation The -deployScope option modifies the output only when the is role "develop-server".
Action Correct the option setting.
WSWS3734W: Warning: Exception caught from invocation to {0}:
Explanation An unexpected exception was caught during the dispatching of the message.
Action Determine source of exception using the class name of the dispatcher and the call stack presented in the message. If it is from an external provider, contact the provider for resolution. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
WSWS3735E: Error: The XML Schema 'extension' within a 'redefine' is not currently supported.
Explanation WSDL2Java does not support 'redefine' elements with 'extension's.
Action Correct your wsdl or schema. Completely define the type within the 'redefine'.
WSWS3736I: Info: SSL connection info is {0} .
Explanation None.
Action None.
WSWS3737I: Info: Found programmatically set SSL thread properties = {0} with listener = {1} registered.
Explanation Runtime has found SSL properties programmatically set on the current thread. The same properties are registered with the event listener. SSL properties programmatically set always have the highest precedence.
Action If this is not intended, application should not programmatically set the properties prior to invocation.
WSWS3738I: Info: Found SSL configuration alias = <{0}> and SSL certificate alias = <{1}> from the message context.
Explanation Based on the JAX-RPC model, the SSL configuration alias or SSL certificate alias can be specified and may have been found from the message's context. The information is used for the SSL connection of the current invocation. However, there may not be value for each alias if the alias has never been specified.
Action If this is not intended, application should not set the properties prior to invocation. Read InfoCenter for further information.
WSWS3739W: Warning: Unable to resolve for an SSL configuration. Explicitly request JSSE properties from security's JSSEHelper.
Explanation WebSphere SSL runtime failed to resolve for an effective SSL configuration. Attempt to default to the JSSE system properties.
Action Make sure SSL configuration is properly set for this invocation following the precedence rules specified in the WebSphere InfoCenter.
WSWS3740E: Error: No SSL configuration is available for endpoint - {0}
Explanation Runtime failed to resolve for an effective SSL configuration with the specified endpoint.
Action Make sure SSL configuration is properly set for this endpoint following the precedence rules specified in the WebSphere InfoCenter.
WSWS3741I: Info: JSSEHelper from Security returns SSL properties = {0} with listener = {1} registered.
Explanation Received SSL properties from the WebSphere security. The same properties are registered with the event listener.
Action None.
WSWS3742I: Info: Mark SSL configuration object {0} to be deleted.
Explanation Internal operation.
Action None.
WSWS3743I: Info: Outbound connection object {0} for address {1} has been invalidated.
Explanation Internal operation. The connection object marked is not usable.
Action None.
WSWS3744I: Info: With matching address {0}, found the associated connection object {1} to be invalidated.
Explanation Internal operation. The connection object invalidated is not usable.
Action None.
WSWS3745I: Info: Return an outbound connection object: {0} that is in invalid state.
Explanation Internal operation.
Action None.
WSWS3746W: Warning: Caught {0}. Query again from the Unified Clustering Framework.
Explanation This exception may be due to a timing problem caused by the asynchronous operation done by the Unified Clustering Framework. The web services engine will attempt to query from the UCF again.
Action None.
WSWS3747W: Warning: Second query from the Unified Clustering Framework failed. No ChannelTarget object is returned from the Unified Clustering Framework.
Explanation The second query fails, the engine proceed to next option using default channels.
Action If Unified Clustering is needed, this is an error. Please check the trace for any error from the clustering.
WSWS3748I: Info: Returned ChannelTarget object from the Unified Clustering Framework: {0}
Explanation None.
Action None.
WSWS3749I: Info: Loading Document at: {0}, Attempt {1}
Explanation None.
Action None.
WSWS3750W: Warning: Class: {0}, is of type java.util.Collection. This is NOT a supported JAX-RPC type, however generation will NOT be suspended.
Explanation The application uses a type that is not a JAX-RPC supported type. Although we proceed with generating artifacts, it's use is NOT supported.
Action Modify your application to use a type that is not a java.util.Collection type, use custom data mappings to map the Collection type, or use it as-is, at your own risk.
WSWS3751E: Error: The ServiceName in the WSADDRESSING_DESTINATION_EPR {0} does not match the service originally configured {1}
Explanation New WS-Addressing destination EPR is being set. However, the service name from the EPR does not match the original service name configured in this object.
Action Enable WS-Addressing trace and check for WS-Addressing errors.
WSWS3752I: (C) COPYRIGHT International Business Machines Corp. 1997, 2007.
Explanation Standard IBM Copyright.
Action No user action is required.
WSWS3753I: IBM WebSphere Application Server Release 6.1
Explanation Standard IBM banner displayed by the web services emitter.
Action No user action is required.
WSWS3754I: Web services Java2WSDL emitter.
Explanation Standard IBM banner displayed by the Java to WSDL emitter.
Action No user action is required.
WSWS3755I: Web services WSDL2Java emitter.
Explanation Standard IBM banner displayed by the WSDL to Java emitter.
Action No user action is required.
WSWS3756E: Invalid HTTP host value. Host value is {0} within the given URL {1}
Explanation Invalid HTTP host value. This could be an internal error.
Action None.
WSWS3757E: Invalid HTTP port value. Port value is {0} within the given URL {1}
Explanation Invalid HTTP port value. This could be an internal error.
Action Modify or add valid port to the endpoint URL.
WSWS3758I: Local cell name: {0}. Mapped cell name from DWLM client: {1}.
Explanation Provide information about local and mapped cell names. The mapped cell name can be from a remote cluster.
Action No user action is required.
WSWS3759E: {0} encountered. Failed to evaluate the WS-Addressing EPR.
Explanation Unable to evaluate the current EPR in the WS-Addressing runtime.
Action Make sure the EPR is set properly. Enable WS-Addressing trace for details.
WSWS3760I: A re-directed asynchronous delivery is detected. Switch to sendSOAPRequestAsync() for {0}
Explanation Uses sendSOAPRequestAsync() to make a re-directed asynchronous delivery. This happens only with re-directed asynchronous delivery due to WS-Addressing.
Action No user action is required.
WSWS3761I: Connection object: {0} will be returned later in the callback object: {1} due to an asynchronous delivery.
Explanation Informational.
Action No user action is required.
WSWS3762I: A response has been received for the previous asynchronous delivery using: {0} and {1}
Explanation Informational. Look for this message to track the response received for the previous asynchronous delivery caused by WS-Addressing.
Action No user action is required.
WSWS3763E: An error has been received in the previous asynchronous delivery using: {0} and {1}
Explanation Look for this message to check error in the previous asynchronous delivery caused by WS-Addressing.
Action Check for the exception logged after this message.
WSWS3764E: Error: The PortName in the WSADDRESSING_DESTINATION_EPR {0} does not match the port originally configured {1}
Explanation New WS-Addressing destination EPR is being set. However, the port name from the EPR does not match the original port name configured in this object.
Action Enable WS-Addressing trace and check for WS-Addressing errors.
WSWS3765W: Warning: The substitution group reference in the schema construct named {0} will be ignored by WSDL2Java.
Explanation WSDL2Java does not currently support XML schema substitution groups. Any reference to a substitution group is ignored.
Action Modify your WSDL or do not expect substitution group designations in generated artifacts.
WSWS3766W: Warning: The argument "{0}" for the elementFormDefault option is invalid. Valid arguments are <qualified | unqualified>. Java2WSDL will ignore this option.
Explanation Java2WSDL only uses qualified or unqualified for the elementFormDefault option.
Action Modify your Java2WSDL invocation to include a valid argument for the elementFormDefault option.
WSWS3767W: Warning: The argument "{0}" for the attributeFormDefault option is invalid. Valid arguments are <qualified | unqualified>. Java2WSDL will ignore this option.
Explanation Java2WSDL only uses qualified or unqualified for the attributeFormDefault option.
Action Modify your Java2WSDL invocation to include a valid argument for the attributeFormDefault option.
WSWS3768W: Warning: The WSDL2Java emitter has found relative namespace: {0}
in the WSDL or schema file. Relative namespaces are neither WS-I compliant, nor compliant
in usage with WS-Security with digital signatures due to C14N restrictions.
Explanation The WSDL or schema file contains relative namespaces, such as "/home".
Action When you use relative namespaces, you may have problems interoperating with other vendors and will encounter security limitations. Consider converting the relative namespaces to absolute namespaces.
WSWS3769W: Unkown option: "{0}". This entry will be ignored.
Explanation This option or property is not recognized by the emitters. The tooling will ignore it.
Action Check the spelling or case used for the properties names and values and correct any errors.
WSWS3770W: Warning: WSDL2Java does not support {0} binding namespace.
Explanation WSDL2Java encountered unsupported binding namespace {0} and will continue code generation process for the supported binding(s).
Action To remove this warning, remove the unsupported binding namespace from your WSDL.
WSWS3938E: The message is enclosed in {0} tags. As stated in the Basic Profile 1.1 Specification Rule R9980, the message must be in a SOAP Envelope.
Explanation The SOAP Envelope must be the root element of the message.
Action Correct the message to be compliant with Web services interoperability standards or work with your Web services provider.
WSWS4100E: Method {0} of class {1} is not supported in SAAJ 1.2.
Explanation The indicated method requires SAAJ 1.3 support. This support is not available in the the installed version of WebSphere.
Action Use an SAAJ 1.2 method or upgrade to a new version of WebSphere.
WSWS4101E: Method {0} of class {1} is not supported in SAAJ 1.2 and DOM Level 2.
Explanation The indicated method requires DOM Level 3, which is part of the SAAJ 1.3 support. This method is not available in the installed version of WebSphere.
Action Use a DOM Level 2 method or upgrade to a new version of WebSphere.
WSWS4102E: The {0} is not available with the Dynamic SOAP protocol.
Explanation The request information is not available when the SOAPConstants.DYNAMIC_SOAP_PROTOCOL is used.
Action Create the SOAP messaage with a SOAP 1.1 or SOAP 1.2 protocol.
WSWS4103E: Method {0} of class {1} is only valid for messages that use the SOAP 1.2 Protocol. The current message uses the {2} protocol.
Explanation The indicated method is only valid for the SOAP 1.2 Protocol. This requirement is defined by the SAAJ 1.3 specification.
Action Use method that is valid for your SOAP Protocol.
WSWS4104E: A {0} is not supported by SAAJ 1.2.
Explanation The indicated protocol requires SAAJ 1.3 support. This support is not available in the the installed version of WebSphere.
Action Use the SOAP 1.1 protocol or upgrade to a new version of WebSphere.
WSWS4105E: The iterator returned from the {0} method does not support the remove() method.
Explanation Some iterators do not support the remove() method. You cannot call this method on the indicated iterator.
Action Do not use the remove method on the iterator.
WSWS4106E: The Fault Reason node does not have a Text node that matches the Locale {0}.
Explanation This behavior is defined by the javax.xml.soap.SOAPFault.getFaultReasonText(Locale) method.
Action Inspect your logic for errors.
WSWS4107E: A Fault Reason node was expected, but was not found while invoking method {0}
Explanation This behavior is defined by the javax.xml.soap.SOAPFault interface.
Action Inspect your logic for errors.
WSWS4108E: A Fault Code node was expected, but was not found while invoking method {0}
Explanation This behavior is defined by the javax.xml.soap.SOAPFault interface.
Action Inspect your logic for errors.
WSWS4109E: MessageFactory.createMessage() when the protocol is "Dynamic Protocol".
Explanation The method is only supported for "SOAP 1.1 Protocol" and "SOAP 1.2 Protocol".
Action Use the correct protocol.
WSWS4110E: The {0} method is not available with the Dynamic SOAP protocol.
Explanation The method cannot be called if the SOAPConstants.DYNAMIC_SOAP_PROTOCOL is used.
Action Use the SOAP 1.1 or SOAP 1.2 protocol.
WSWS4111E: Namespace {0} is not valid with protocol {1}.
Explanation The specified namespace does not match a uri associated with the specified protocol.
Action You may have a problem with your SOAP message.
WSWS4112E: {0} is not recognized SOAP Protocol.
Explanation The specified protocol is not a recognized protocol.
Action Use one of the following protocols javax.xml.soap.SOAPConstants.SOAP_1_1_PROTOCOL, javax.xml.soap.SOAPConstants.SOAP_1_2_PROTOCOL, or javax.xml.soap.SOAPConstants.DYNAMIC_SOAP_PROTOCOL.
WSWS4113E: {0} is not supported on a {1} object.
Explanation The specified method is not a supported on the specified object.
Action Correct your code.
WSWS4114E: The SOAPBody.extractContentAsDocument() method failed because the body contains {0} elements.
Explanation The method requires that the body contain exactly one element.
Action Correct your code.
WSWS4115E: The message has an CONTENT_TYPE of {0}. A CONTENT_TYPE of {1} or {2} was expected.
Explanation The engine uses the CONTENT_TYPE to determine whether the message is a SOAP 1.1 or SOAP 1.2 message.
Action Correct the inbound message.
WSWS4116E: An attempt was made to invoke SOAPElement.addChildElement(name, prefix) with a prefix that was not bound to a namespace. The prefix is {0} and the name is {1}.
Explanation SAAJ 1.3 requires that the prefix be bound. This means that a namespace declaration must exist in an ancestor element.
Action Correct the code that called addChildElement.
WSWS4117E: An attempt was made to add an SOAPEnvelope with a protocol of {0} to a SOAPMessage with a protocol of {1}.
Explanation The SOAPEnvelope and SOAPMessage must have the same protocol.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS4118E: An attempt was made to get data from an attachment that does not have a data handler. The attachment content id is {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
WSWS4120E: An attempt was made to set an invalid Fault Code. The faultCode localName is {0}; namespace is {1}.
Explanation SAAJ 1.3 requires that the Fault Code must be one of the fault codes defined in the version of SOAP specification in use.
Action Correct the Fault Code.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: May 16, 2012 4:38:33 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.engine.resources.engineMessages.html

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