|
WebSphere WebServices Engine
|
|
WSWS3000I: WSDL2Java emitter
Usage: WSDL2Java [options] WSDL-URI
Important Options:
-r, -role
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
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
output directory for emitted files.
-m, -inputMappingFile
the location of the Java to WSDL mapping.
Other Options:
-h, -help
print this message and exit.
-X, -helpX
print extended options.
-v, -verbose
print verbose informational messages.
-N, -NStoPkg =
mapping of namespace to package.
Alternatively declare this information in the mapping file.
-O, -timeout
number of seconds to wait for accessing WSDL-URI.
(default is 45 seconds), specify -timeout -1 to disable.
-g, -genResolver
generate an absolute-import resolver.
-u, -useResolver
specify an absolute-import resolver to use during parsing.
-d, -deployScope
indicates how to deploy the server.
Valid arguments are: "Request", "Session", "Application".
Explanation
These are the options to WSDL2Java.
User Response:
Use the specified options when invoking WSDL2Java.
WSWS3001I: Info:
Extended Options:
-U, -user
login username to access the WSDL-URI.
-P, -password
login password to access the WSDL-URI.
-a, -all
generate java files for all types, even unreferenced ones.
-t, -testCase
emit template junit testcase class for testing web service.
-D, -Debug
print debug information.
-f, -fileNStoPkg
file of NStoPkg mappings (default NStoPkg.properties).
-j, -genJava
generate Java files. Valid arguments are:
"No"
"IfNotExists" (default)
"Overwrite"
-x, -genXML
generate XML and XMI files. Valid arguments are:
"No"
"IfNotExists" (default)
"Overwrite"
Explanation
These are the extended options to WSDL2Java.
User Response:
These are advanced options that users should not generally use.
WSWS3002I: Java2WSDL emitter
Usage: Java2WSDL [options] class-of-portType
Options:
-location
web service location url
-output
output WSDL file name
-input
input wsdl file name
used to build wsdl from existing wsdl information
-style
valid arguments:
rpc (the default): generate rpc style wsdl
document: generate document style wsdl
-use
valid arguments:
encoded (default if rpc): encoded use
literal (default if document): literal use
-transport
valid arguments:
http: generate a soap http binding
jms: generate a soap jms binding
defaults to http unless -location indicates jms
-portTypeName
name of the portType
defaults to name of the input class
-bindingName
name of the binding
defaulted from portType if not specified
-serviceElementName
name of the service
defaulted from portType name if not specified
-servicePortName
port
name of the port
defaulted from -location if not specified
-namespace
target namespace of wsdl
-PkgtoNS
=
mapping of package names to namespaces
-implClass
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
other classes that should be added to the wsdl
-verbose
display verbose messages
-help
displays this message
-helpX
displays extended options
Explanation
These are the options to Java2WSDL.
User Response:
Use the specified options when invoking Java2WSDL.
WSWS3003I: Info:
Extended Options:
-wrapped
indicate if wsdl should respect "wrapped" rules
valid only for literal use.
-stopClasses
space or comma separated list of class names which will stop
inheritance search when processing classes
-soapAction
valid arguments:
OPERATION sets soapAction field to the operation name.
NONE sets soapAction field to "".
DEFAULT uses deployment information to set the field.
-outputImpl
specify if you want both interface and implementation wsdls
-locationImport
location of interface WSDL file
-namespaceImpl
target namespace for implementation WSDL
-MIMEStyle
valid arguments:
Axis (default): Axis style MIME representation
WSDL11: WSDL 1.1 MIME representation
-voidReturn
valid arguments:
ONEWAY:treat methods with void returns as one-way
TWOWAY:treat methods with void returns as two-way
-debug
display debug messages
Explanation
These are the extendedoptions to Java2WSDL.
User Response:
These are advanced options that users should not generally use.
WSWS3004W: Warning: The -location was not set, the value "{0}" is used instead.
Explanation
The -location option is a required option.
User Response:
Please specify the -location option.
WSWS3005W: Warning: The -server-side option must have an argument that is Bean or EJB. Defaulting to Bean.
Explanation
The -server-side option is incorrect.
User Response:
Please specify the correct -server-side option.
WSWS3006W: Warning: The argument of the -transport option must be "jms" or "http". The default setting ("http") will be used.
Explanation
The -transport option is incorrect.
User Response:
Please specify the correct option.
WSWS3007E: Error: The {0} operation of {1} has an output element. This output element is removed and the operation is changed to one-way.
Explanation
This pre-existing operation has an output element. It is removed.
User Response:
None.
WSWS3008E: Error: The {0} operation of {1} has a fault element. The faults are removed and the operation is changed to one-way.
Explanation
This pre-existing operation has a fault element. It is removed.
User Response:
None.
WSWS3009I: Info: Loading Class {0}
Explanation
Loading specified class.
User Response:
None.
WSWS3010I: Info: Generating {0} {1}
Explanation
Generating indicated construct.
User Response:
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.
User Response:
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.
User Response:
Correct the JMS endpoint URL and re-try.
WSWS3013E: The JMS endpoint URL is missing one or more of the following required properties: connectionFactory, destination, targetService
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.
User Response:
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.
User Response:
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.
User Response:
Ensure that the JNDI name is correct.
WSWS3016E: Caught JMSException: {0}
Explanation
A JMS operation resulted in the specified JMSException.
User Response:
Use the detailed information in the original error message to determine how to correct the problem.
WSWS3017E: Linked Exception: {0}
Explanation
None.
User Response:
None.
WSWS3018E: Caught exception during request processing: {0}
Explanation
The specified exception occurred while a request was being processed.
User Response:
Use the detailed information in the original error message to determine how to correct the problem.
WSWS3019E: Caught WebServicesFault: {0}
Explanation
The specified WebServicesFault exception occurred.
User Response:
Use the detailed information in the original error message to determine how to correct the problem.
WSWS3020E: Error getting server engine.
Explanation
The web services message-driven bean listener was unable to retrieve a configured server engine during its initialization.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
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.
User Response:
Ensure that any services which use topic destinations contain only one-way operations.
This means that within the WSDL file, the operation does not contain an 'output' message.
WSWS3024E: Root part containing SOAP envelope not found. contentId = {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3025E: Error: Could not locate a parameter named {0} for {1}.
Explanation
Suspect a bad mapping file supplied to WSDL2Java.
User Response:
Correct your mapping file.
WSWS3026E: Error: The argument of the -voidReturn option must be "oneway" or "twoway".
Explanation
The -voidReturn option is incorrect.
User Response:
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.
User Response:
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.
User Response:
Ensure that the _Helper class was properly emitted by WSDL2Java and deployed correctly.
WSWS3029W: Warning: The xml construct named {0} cannot be mapped to a java type. The construct will be mapped to javax.xml.soap.SOAPElement.
Explanation
Some xml constructs cannot be mapped to java types.
User Response:
The application code will need to use the SOAPElement methods to construct and analyze the data.
WSWS3030E: Error: An internal error occurred while trying to locate the target method. Debug:{0}
Explanation
An internal error occurred. Possibly due to an error in the deployment infornation.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3031E: Error: Serialization cannot occur for {0}. There are no registered type mappings.
Explanation
The indicated object cannot be serialized.
User Response:
Make sure that a proper serializer is registered.
WSWS3032E: Error: Attempt to get a secure socket factory using KeyStore: {0}, TrustStore: {1}, Cryptographic token in: {2}
Explanation
Could not get a secure socket factory.
User Response:
Correct your KeyStore configuration.
WSWS3033E: Error: Deserialization cannot occur for {0}.
Explanation
The indicated type cannot be deserialized.
User Response:
Make sure that a proper deserializer is registered.
WSWS3034E: Error: The OperationDesc for {0} was not matched to a method of {1}. Debug:{2}
Explanation
Internal error caused by improper startup code.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
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.
User Response:
Correct Handler code to eliminate RuntimeException.
WSWS3037E: Error: Serialization cannot occur for {0}.
Explanation
The indicated object cannot be serialized.
User Response:
Make sure that a proper serializer is registered.
WSWS3038E: Error: Deserialization cannot occur for {0}. There are no registered type mappings.
Explanation
The indicated type cannot be deserialized.
User Response:
Make sure that a proper deserializer is registered.
WSWS3039E: Error: Resource has been deleted.
Explanation
Trying to access a deleted memory managed data source.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3040E: Error: Malformed arrayType value ''{0}''
Explanation
The arrayType attribute in the soap message is invalid.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3041E: Error: Bad authentication type (I can only handle "Basic").
Explanation
Only Basic authentication is supported with the SimpleServerEngine.
User Response:
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'.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3043E: Error: Unexpected characters in a calendar value.
Explanation
A calendar value in a soap message was invalid.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3044E: Error: Bad character or insufficient number of characters in hex string.
Explanation
A character in a hex string was invalid.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3045E: Error: Invalid date.
Explanation
A bad date value was found in a soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3046E: Error: Invalid date/time.
Explanation
A bad date/time value was found in a soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3047E: Error: Cannot deserialize element {1} of bean {0}.
Explanation
The specified bean does not have a property that matches the element. The soap message cannot be deserialized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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 nt extend the Handler class.
User Response:
Correct your deployment information. CMSG0002
WSWS3049E: Error: A bad Holder class was encountered.
Explanation
An attempt was made to use the specified class as a Holder. However the class does not extend the Holder interface.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3052E: Error: Bad envelope namespace: {0}
Explanation
The envelope element of the soap message has an incorrect namespace. The message cannot be deserialized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3053E: Error: An attempt was made to construct a Name object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3054E: Error: An attempt was made to construct a NCName object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3055E: Error: An attempt was made to construct a NegativeInteger object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3056E: Error: An attempt was made to construct a NMToken object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3057E: Error: An attempt was made to construct a NonNegativeInteger object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3058E: Error: An attempt was made to construct a NonPositiveInteger object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3060E: Error: Invalid Parameter mode {0}.
Explanation
Internal exception of the WSDL2Java emitter.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3062E: Error: portName should not be null.
Explanation
The portName argument to the Service.getCalls method must be a recognized port name.
User Response:
Ensure that the argument to the Service.getCalls method is appropriate.
WSWS3063E: Error: An attempt was made to construct a PosInteger object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3064E: Error: Cannot handle non-GET, non-POST request.
Explanation
SimpleServerEngine does not understand the request.
User Response:
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.
User Response:
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3067E: Error: Invalid time.
Explanation
A bad time value was found in a soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3068E: Error: Invalid timezone.
Explanation
A bad timezone was found in a soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3069E: Error: Found languageSpecificType namespace ''{0}'', expected ''{1}''
Explanation
A problem has occurred in the deployment software.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3070E: Error: An attempt was made to construct an UnsignedByte object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3071E: Error: An attempt was made to construct an UnsignedShort object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3072E: Error: An attempt was made to construct an UnsignedInt object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3073E: Error: An attempt was made to construct an UnsignedLong object with an invalid string.
Explanation
Normally this is caused by an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3074E: Error: Cannot add a second body to a soap envelope.
Explanation
This error could be the result of an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3075E: Error: User ''{0}'' not authenticated (unknown user).
Explanation
User cannot be authenticated.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3076E: Error: User ''{0}'' not authenticated.
Explanation
User cannot be authenticated.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3077E: Error: User ''{0}'' not authorized to ''{1}''
Explanation
User is not authorized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3078E: Error: Cannot convert {0} to bytes.
Explanation
Internal Error: The soap message cannot be converted into bytes.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3079E: Error: Cannot convert form {0} to String.
Explanation
Internal Error: The soap message cannot be converted into a String.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3080E: Error: Could not convert {0} to bean field ''{1}'', type {2}
Explanation
The indictated value could not be assigned to the bean field. The soap message cannot be deserialized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3081E: Error: Could not convert value to int.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3082E: Error: Cannot serialize null arrays.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3083E: Error: getURL failed to correctly process URL; protocol not supported.
Explanation
Tool option error. See other messages.
User Response:
Fix the URL.
WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3085E: Error: Cannot invoke Call with null namespace URI for method {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3086E: Error: Cannot serialize a {0} with the ArraySerializer.
Explanation
The indicated class cannot be serialized with the array serializer.
User Response:
Suspect a problem with the deployment information.
WSWS3087E: Error: Cannot serialize non-Elements with an ElementSerializer.
Explanation
The element serializer can only be used to serialize org.w3c.dom.Element objects.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3088E: Error: Cannot serialize a raw object with the SimpleSerializer.
Explanation
The SimpleSerializer cannot be used to serialize a non-registered object.
User Response:
Make sure your this class is registered with an appropriate type.
WSWS3089E: Error: Cannot set location URI: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3090E: Error: Unable to tunnel through {0}:{1}. Proxy returns "{2}"
Explanation
Can't make the appropriate tunnel.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3091E: Error: Changing admin password.
Explanation
Changed passwords on AdminClient.
User Response:
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 webservices team. if this problem is occurring in the runtime.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3093E: Error: Could not create Call object in AdminClient.
Explanation
Internal Error.
User Response:
Don't use AdminClient.
WSWS3094E: Error: WSDDPort couldn't construct provider!
Explanation
Internal Error with deployment software.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3095E: Error: Connection closed.
Explanation
The connection is closed. The remote service call cannot be made.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
Fix your wsdl or use the NStoPkg options to differentiate the classes.
WSWS3097E: Error: Emitter failure. All input parts must be listed in the parameterOrder attribute of {0}
Explanation
The parameter order attribute in the wsdl is incorrect.
User Response:
Fix your wsdl.
WSWS3098E: Error: Emitter failure. Cannot find endpoint address in port {0} in service {1}
Explanation
The endpoint address cannot be found.
User Response:
Fix your wsdl.
WSWS3099E: Error: Emitter failure. Invalid endpoint address in port {0} in service {1}: {2}
Explanation
The endpoint address is invalid.
User Response:
Fix your wsdl.
WSWS3100E: Error: Emitter failure. No binding found for port {0}
Explanation
Specify a binding on the service wsdl port.
User Response:
Fix your wsdl
WSWS3101E: Error: Emitter failure. No binding entry found for {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3102E: Error: Emitter failure. No portType entry found for {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3103E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document.
Hint: make sure
is fully qualified.
Explanation
The binding must be defined if referenced.
User Response:
Fix the WSDL.
WSWS3104E: Error: Emitter failure. There is an undefined binding ({0}) in the WSDL document {1}.
Hint: make sure
is fully qualified.
Explanation
The binding must be defined if referenced.
User Response:
Fix the WSDL.
WSWS3105E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document.
Hint: make sure is fully qualified.
Explanation
The portType must be be defined if referenced.
User Response:
Fix the WSDL.
WSWS3106E: Error: Emitter failure. There is an undefined portType ({0}) in the WSDL document {1}.
Hint: make sure is fully qualified.
Explanation
The portType must be defined if referenced.
User Response:
Fix the WSDL.
WSWS3107E: Error: Generic Error.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3108E: Error: Error: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3109E: Error: Error invoking webservice operation: {0}
Explanation
Problem occurred invoking remote web service.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3110E: Error: Error processing ''{0}''
Explanation
Admin error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3111E: Error: Error determining if {0} already exists. Will not generate this file.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3112E: Error: Generating WebServicesFault due to missing SOAPAction.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3113E: Error: Cannot add a second header to a soap envelope.
Explanation
This error could be the result of an invalid soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3114E: Error: Internal error.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3115E: Error: Configuration file directory ''{0}'' is not readable.
Explanation
The specified directory cannot be read.
User Response:
Fix your configuration.
WSWS3116W: Warn: PERFORMANCE ALERT: The following message is re-parsed: {0}
Explanation
Non performant serialization encountered.
User Response:
Examine code and make appropriate changes.
WSWS3117E: Error: Invalid container type (expected "ejb", "web", "client" or "none"), defaulting to "none".
Explanation
The -container option of WSDL2Java is wrong.
User Response:
Fix the option setting.
WSWS3118E: Error: Invalid role (expected "develop-client", "deploy-client", "develop-server", or "deploy-server"), defaulting to "develop-client".
Explanation
The -role option of WSDL2Java is wrong.
User Response:
Fix the option setting.
WSWS3119E: Error: Invalid option combination: -role develop-server and -container client or -container none are invalid. The -container will be defaulted to "web".
Explanation
The webservice always runs in a web or ejb container.
User Response:
Fix the options and rerun WSDL2Java.
WSWS3120E: Error: Configuration is missing.
Explanation
Deployment error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3121I: Info: {0} is a oneway operation.
Explanation
informational message.
User Response:
no action required.
WSWS3122E: Error: Could not find service {0} referenced in URI {1}
Explanation
The specified service could not be found.
User Response:
Check the name of the service specified by the client and the deployment of that service on the server.
WSWS3123E: Error: Javaclass {0} specified for handler {1} must implement {2} OR {3}. The handler will be skipped.
Explanation
A configuration file (was-webservices.xml) defines a handle javaclass that does not implement the expected interface.
User Response:
Specify javaclass that implements the expected interface.
WSWS3124E: Error: Invalid -genJava option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Explanation
The -genJava option of WSDL2Java is wrong.
User Response:
Correct the option setting.
WSWS3125E: Error: Invalid -genXML option argument, valid are "No", "IfNotExists", or "Overwrite". Defaulting to "IfNotExists".
Explanation
The -genXML option of WSDL2Java is wrong.
User Response:
Correct the option setting.
WSWS3126E: Error: Could not get a secure socket factory from the following SSL Configuration: {0}.
Explanation
Could not get a secure socket factory.
User Response:
Correct your SSL configuration.
WSWS3127E: Error: Invalid WSDD element ''{0}'' (wanted ''{1}'').
Explanation
Error occurred during deployment. This is probably an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3128E: Error: Could not make envelope from bytes.
Explanation
This could possibly due to a deserialization error. Look for other errors.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
Correct the invocation of the getPort method.
WSWS3130E: Error: Only interfaces which extend java.rmi.Remote may be used for the proxy Class argument of the Service.getPort method.
Explanation
The proxy Class argument must be an interface that extends java.rmi.Remote.
User Response:
Fix the invocation of the getPort method.
WSWS3131E: Error: Must specify a password for AdminClient.
Explanation
A password must be supplied.
User Response:
AdminClient is not fully supported.
WSWS3132E: Error: No target service was found.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3133E: Error: Need to specify a user for authorization.
Explanation
No user was found to authorize.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3134E: Error: Remote administrator access is not allowed.
Explanation
Cannot administor remotely.
User Response:
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3136E: Error: No deserializer defined for array type {0}
Explanation
The array of the indicated component type could not be deserialized.
User Response:
This problem may be due to invalid deployment information.
WSWS3137E: Error: No deserialization context to use in SOAPElement.convertToObject().
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3138E: Error: No custom elements allowed at top level until after the
tag.
Explanation
The soap message is invalid and cannot be deserialized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3139E: Error: No deserializer for {0}
Explanation
Normally this is the result of bad client or server deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3141E: Error: Could not get DOM document: XML was "{0}"
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3142E: Error: Could not find WebServices engine.
Explanation
Probably an Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3143W: Warning: Expected instance of ''EngineConfiguration'' in environment.
Explanation
Invalid configuration data.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3144E: Error: Cannot locate handler: {0}
Explanation
Internal Error with deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3145E: Error: No HandlerProvider ''handlerClass'' option was specified.
Explanation
Missing information in deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3146E: Error: No handlers in {0} ''{1}''
Explanation
Missing handlers in deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3147E: Error: no {0} header!
Explanation
Header missing in soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3150E: Error: No provider type matches QName ''{0}''
Explanation
Deployment information is not complete. This is probably the result of an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3151E: Error: No operation name specified.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3152E: Error: Cannot find operation: {0} - none defined
Explanation
The WSDL does not define any operations in the portType.
User Response:
This is an internal error or deployment error.
WSWS3153E: Error: Cannot find operation: {0}
Explanation
The WDSL binding did not specify the operation.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3154E: Error: No ''{0}'' option was configured for the service ''{1}''
Explanation
The indicated option was not found.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3155E: Error: {0} not found as an input part OR an output part.
Explanation
The parameter order attribute must reference a message part.
User Response:
Correct the WSDL.
WSWS3156E: Error: Cannot find port: {0}
Explanation
The specified port could not be found by Service.getPort.
User Response:
Correct the invocation of Service.getPort.
WSWS3157E: Error: Cannot find portType: {0}
Explanation
The deployed wsdl is missing the portType.
User Response:
Correct the deployed wsdl.
WSWS3158E: Error: No request message in MessageContext?
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3159E: Error: No serializer found for class {0} in registry {1}
Explanation
Usually this indicates a internal error with the deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3160E: Error: Cannot find service: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3161E: Error: No service has been defined.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3162E: Error: No service object defined for this Call object.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3163E: Error: The WebServices engine could not find a target service to invoke! targetService is {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3164E: Error: No security provider in MessageContext.
Explanation
Make sure a security provider is configured.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3165E: Error: No HTTP SOAPAction property in context.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3166E: Error: No client transport named ''{0}'' found.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3167E: Error: No transport mapping for protocol: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3168E: Error: No mapped schema type for {0}
Explanation
The indicated array component type cannot be serialized. Make sure this type is registered.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3169E: Error: Component requires a type attribute.
Explanation
The component of the vector cannot be deserialized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3170E: Error: Must include type attribute for Handler deployment!
Explanation
Missing deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3171E: Error: No type QName for mapping!
Explanation
Missing deployment information in the type mapping registry.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3172E: Error: User ''{0}'' not authorized to ''{1}''
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3173E: Error: Did not understand "MustUnderstand" header(s):{0}
Explanation
Handler did not understand mustUnderstand headers.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3174E: Error: No value field for RPCParam to use. {0}
Explanation
Internal Exception.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3175E: Error: {0} is null.
Explanation
Processing cannot continue because the indicated item is null.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3176E: Error: AdminClient did not initialize correctly: ''call'' is null!
Explanation
Internal Error.
User Response:
AdminClient is not fully supported.
WSWS3177E: Error: Null namespace URI specified.
Explanation
Namespace argument must be specified.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3178E: Error: null parent.
Explanation
Tried to call SAAJ setParent with a null argument. This may be the result of an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3179E: Error: Null provider type passed to WSDDProvider.
Explanation
Missing deployment information. This may be the result of an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3180E: Error: Null response message.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3181E: Error: Odd number of digits in hex string.
Explanation
The HexBinary object cannot be constructed.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
This could be a DII or internal error.
WSWS3185I: Info: Parsing XML file: {0}
Explanation
informational message.
User Response:
no action required.
WSWS3186E: Error: Error in parsing: {0}
Explanation
Problem occurred deserializing the soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3187E: Error: Processing file {0}
Explanation
AdminClient error processing the indicated file.
User Response:
AdminClient is not fully supported.
WSWS3188I: Info: {0} quitting.
Explanation
informational message.
User Response:
no action required.
WSWS3189E: Error: Administration service requested to quit, quitting.
Explanation
Admin quitting.
User Response:
Admin class is not fully supported.
WSWS3190E: Error: Unable to bind to port {0}. Did not start SimpleServerEngine.
Explanation
Internal Error.
User Response:
SimpleServerEngine not fully supported.
WSWS3191I: Info: Configuration file read-only so engine configuration changes will not be saved.
Explanation
informational message.
User Response:
no action required.
WSWS3192E: Error: return code: {0}
{1}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3193E: Error: Problem with servlet engine /WEB-INF directory
Explanation
/WEB-INF may not be accessible.
User Response:
Correct problem with WEB-INF directory.
WSWS3194E: Error: Problem with servlet engine config file: {0}
Explanation
config file may not be accessible.
User Response:
Correct problem with servlet engine config file.
WSWS3195W: Warn: Unable to load/create servlet engine config file, attempting internal default (from jar).
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
no action required.
WSWS3196E: Error: Problem with servlet engine config file (loading from jar).
Explanation
Configuration error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3197I: Info: {0} starting up on port {1}.
Explanation
informational message.
User Response:
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.
User Response:
Correct the deployed wsdl.
WSWS3199E: Error: Unexpected end of stream.
Explanation
Internal Error or problem with input soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3200E: Error: Unknown host - could not verify admininistrator access.
Explanation
Unknown host encountered by Admin tool.
User Response:
The Admin tool is not fully supported.
WSWS3201E: Error: Where {0} looks like:
Explanation
Admin tool error.
User Response:
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.
User Response:
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.
User Response:
Correct your deployment information.
WSWS3204E: Error: {0} already exists.
Explanation
Internal Error in the WSDL2Java SymbolTable.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3205E: Error: Type {0} is referenced but not defined.
Explanation
Your wsdl references types or elements that are not defined.
User Response:
Correct your wsdl.
WSWS3206E: Error: Cannot find EJB at JNDI location {0}
Explanation
There may be a problem with your JNDI configuration.
User Response:
Correct your JNDI configuration.
WSWS3207E: Error: Cannot create InitialContext.
Explanation
An InitialContext was not created.
User Response:
Inspect other errors to determine why InitialContext was not created.
WSWS3208E: Error: The definition of {0} results in a loop.
Explanation
Found recursive definition of the indicated type or element.
User Response:
Correct your wsdl.
WSWS3209E: Error: Bad property. The value for {0} should be of type {1}, but it is of type {2}.
Explanation
A bad propery detected on the Call or MessageContext. This could be caused by an internal error.
User Response:
Fix the property.
WSWS3210E: Error: Null property name specified.
Explanation
A bad property was detected. This could be caused by an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3211E: Error: Null property value specified.
Explanation
A null property value was specified. This could be caused by an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3212E: Error: Property name {0} not supported.
Explanation
An unsupported property is being used.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3213E: Error: Null getter method specified.
Explanation
This is normally due to an internal error associated with the serialization engine.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3214E: Error: Null setter method specified.
Explanation
This is normally due to an internal error associated with the deserialization engine.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3215E: Error: Null public instance field specified.
Explanation
This is normally due to an internal error with the serialization engine.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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 intrnal problem.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3218E: Error: Null serializer factory specified in the TypeMappingImpl.register method.
Explanation
This error normally suggests a problem with the deployment software.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3220E: Error: Error: Empty or missing service name.
Explanation
The WSDL service name is wrong.
User Response:
Correct the WSDL.
WSWS3221E: Error: Bean attribute {0} is of type {1}, which is not a simple type.
Explanation
Attributes must be simple types.
User Response:
Correct the WSDL.
WSWS3222E: Error: Attribute is of type {0}, which is not a simple type.
Explanation
Attributes must be simple types.
User Response:
Correct the WSDL.
WSWS3223E: Error: Exception caught while constructing handler {0}: {1}
Explanation
Problem creating JAXRPC Handler.
User Response:
Review reasons for thrown exception.
WSWS3224I: Info: No disk access, using memory only.
Explanation
informational message
User Response:
No action required.
WSWS3225E: Error: No DeserializerFactory for {0}
Explanation
This normally indicates a problem with the deployed type mapping registry.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3226E: Error: Null FieldDesc specified.
Explanation
Internal Exception.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3227E: Error: Exception:
Explanation
Used for various fatal exceptions. See other messages.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3228E: Error: Exception: {0}
Explanation
Used for various excpeptions. See other messages.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3229E: Error: ConfigurationException:
Explanation
Normally indicates an internal error has occurred.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3230E: Error: ParserConfigurationException:
Explanation
Indicates that an error has occurred while configuring the xml parser.
User Response:
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.
User Response:
Correct the parser configuration.
WSWS3232E: Error: java.net.UnknownHostException:
Explanation
Normally indicates that an internal error has occurred.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3233E: Error: javax.mail.MessagingException:
Explanation
Normlly indicates a problem with a MIME message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3234E: Error: java.io.IOException:
Explanation
Normally an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3235E: Error: java.io.IOException: {0}
Explanation
Normally an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3236E: Error: IllegalAccessException:
Explanation
Normally an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3237E: Error: IllegalArgumentException:
Explanation
This may be issued during overloaded message processing.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3238E: Error: IllegalArgumentException: {0}
Explanation
This error may occur during overloaded method processing.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3239E: Error: InvocationTargetException:
Explanation
A problem occured invoking the indicated target.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3240E: Error: InstantiationException:
Explanation
This error may indicate a problem with MIME attachments.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3241E: Error: MalformedURLException:
Explanation
Malformed URL Exception occurred in the SimpleServerEngine.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3242E: Error: WebServicesFault:
Explanation
A WebServicesFault has occurred.
User Response:
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.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3244I: Info: Mapping Exception to WebServicesFault: {0}
Explanation
informational message. See other messages for details about why the fault was issued.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3245E: Error: WSDL2Java emitter timed out (this often means the WSDL at the specified URL is inaccessible)!
Explanation
Normally indicates that the WSDL is not accessible.
User Response:
Make sure the WSDL is accessible.
WSWS3246E: Error: SOAPFault.addDetail called when a detail is present.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3247E: Error: No endpoint.
Explanation
See other messages for more details.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3248E: Error: Unsupported attachment type "{0}" only supporting "{1}".
Explanation
Indicates that an unsupported attachment type was encountered.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3249E: Error: This attachment implementation accepts only SOAPPart objects as the root part.
Explanation
Interal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.
Explanation
Possibly an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3251E: Error: Stream closed.
Explanation
Tried to access a closed stream.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3252E: Error: End of stream encountered before final boundary marker.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3253E: Error: maxCached value is bad: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3254E: Error: Reset and mark not supported!
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3255E: Error: input buffer is null.
Explanation
Internal Error
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3256E: Error: Offset is negative: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3257E: Error: Length: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3258E: Error: Write beyond buffer.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3259E: Error: Error reading data stream: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3260E: Error: File for data handler does not exist: {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3261E: Error: Error in MIME data stream, start boundary not found, expected: {0}.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3262E: Error: Error in parsing mime data stream: {0}.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3263E: Error: No support for attachments.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3264E: Error: No content.
Explanation
Data Handler has no content.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3265E: Error: No engine configuration file - aborting.
Explanation
Possibly an internal error.
User Response:
Make sure your engine configuration is correct.
WSWS3266E: Error: The element "{0}" is an attachment with sub elements which is not supported.
Explanation
Child elements were not anticipated in the soap message. The soap message cannot be deserialized.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3267E: Error: Error: Missing type resolution for element {2}, in WSDL message part {0} of operation {1}.
Explanation
Your WSDL may be bad.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3268E: Error: The soap:operation for binding operation {0} must have a "use" attribute.
Explanation
Probably an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3269E: Error: Default type mapping cannot be modified.
Explanation
The type mapping cannot be modified after registration has occurred.
User Response:
Please correct your code.
WSWS3270E: Error: Type mapping cannot be modified via delegate.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3271E: Error: Invalid TypeMapping specified: wrong type or null.
Explanation
Invalid TypeMapping registration.
User Response:
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.
User Response:
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.
User Response:
Please change your code.
WSWS3274E: Error: {0}: {1} is not a vector.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3275E: Error: Invalid parameter mode byte ({0}) passed to getModeAsString().
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3276E: Error: Marking streams not supported.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3277E: Error: No such operation ''{0}''
Explanation
This may be a symptom of a web service deployment problem.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3278E: Error: Attempt to set implementation class on a ServiceDesc which has already been configured.
Explanation
Internal Exception.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3280E: Error: The value of -soapAction must be DEFAULT, NONE or OPERATION.
Explanation
A bad argument was specified for -soapAction.
User Response:
Use the correct Java2WSDL -soapAction option.
WSWS3281E: Error: Tried to invoke method {0} with arguments {1}. The arguments do not match the signature.
Explanation
Suspect a problem with the web service deployment or the soap message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3282I: Info: Generating {0}.
Explanation
Informational message indicating which java classes are generated by WSDL2Java.
User Response:
no action required.
WSWS3283E: Error: The value of -style must be DOCUMENT or RPC.
Explanation
The -style option of Java2WSDL is incorrect.
User Response:
Use a correct -style option.
WSWS3284E: Error: Could not find class ''{0}'' for the service.
Explanation
Suspect a webservice deployment error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3285E: Error: Could not find class ''{0}'' for the service ''{1}''.
Explanation
Suspect a webservice deployment error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3286E: Error: The has already been specified as, {0}. It cannot be specified again as {1}.
Explanation
Only one class file may be specified for Java2WSDL.
User Response:
Correct your invocation of Java2WSDL.
WSWS3287E: Error: The was not specified.
Explanation
A class file must be specified for Java2WSDL.
User Response:
Correct your invocation of Java2WSDL.
WSWS3288E: Error: The wsdl URI has already been specified as, {0}. It cannot be specified again as {1}.
Explanation
The WSDL file can only be specified once for WSDL2Java.
User Response:
Correct your invocation of WSDL2Java.
WSWS3289E: Error: The wsdl URI was not specified.
Explanation
The WSDL URI must be specified for WSDL2Java.
User Response:
Correct your invocation of WSDL2Java.
WSWS3290E: Error: Unrecognized {0}: ''{1}''
Explanation
Inappropriate value for the enumeration.
User Response:
Please correct your code.
WSWS3291E: Error: The class {0} is not a bean class and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
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 webservice via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your web service.
WSWS3292E: Error: 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 webservice via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your web service.
WSWS3293E: Error: The class {0} does not contain a default constructor, which is a requirement for a bean class. The class cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file.
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 webservice via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your web service.
WSWS3294E: Error: The XML Schema type ''{0}'' is not currently supported.
Explanation
WSDL2Java does not support this XML Schema type.
User Response:
Correct your wsdl.
WSWS3295E: Error: Message part {0} of operation or fault {1} has no element or type attribute.
Explanation
Each message part must have an element or type attribute which locates the schema element/type.
User Response:
Correct your wsdl.
WSWS3296E: Error: The value of {0} for attachment format must be {1};
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3297E: Error: DIME Type length is {0} which exceeds maximum {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3298E: Error: DIME ID length is {0} which exceeds maximum {1}.
Explanation
Internal Error
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3299E: Error: Max chunk size "{0}" needs to be greater than one.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3300E: Error: Max chunk size "{0}" exceeds 32 bits.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3301E: Error: Each DIME Stream must be read fully or closed in succession.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3302E: Error: DIME stream data not padded correctly.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3303E: Error: Received "{0}" bytes to read.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3304E: Error: Received "{0}" as an offset.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3305E: Error: Array to read is null
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3306E: Error: Array size of {0} to read {1} at offset {2} is too small.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3307E: Error: End of physical stream detected when more DIME chunks expected.
Explanation
Internal Error
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3308E: Error: End of physical stream detected when {0} more bytes expected.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3309E: Error: There are no more DIME chunks expected!
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3310E: Error: DIME header less than {0} bytes.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3311E: Error: DIME version received "{0}" greater than current supported version "{1}".
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3312E: Error: DIME option length "{0}" is greater stream length.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3313E: Error: DIME stream closed during options padding.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3314E: Error: DIME stream closed getting ID length.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3315E: Error: DIME stream closed getting ID padding.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3316E: Error: DIME stream closed getting type.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3317E: Error: DIME stream closed getting type padding.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3318E: Error: DIME stream received bad type "{0}".
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3321E: Error: Invalid normalizedString value.
Explanation
The NormalizedString object could not be set due to an invalid value.
User Response:
Correct the normalizedString value.
WSWS3322E: Error: Invalid token value.
Explanation
The Token object could not be set due to an invalid value.
User Response:
Correct the token value.
WSWS3323E: Internal Error occurred while build the property descriptors for {0}.
Explanation
Internal Error.
User Response:
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
Correct the indicated class.
WSWS3326E: Error: Error looking for paramter names in bytecode: unexpected end of file.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3327E: Error: Error looking for paramter names in bytecode: unexpected bytes in file.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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 webservice via Java2WSDL is not guaranteed.
User Response:
All of the java classes that are part of your web service interface must have appropriate mappings to wsdl. This is necessary so that a client to the service can automatically generate the interface and all related classes in order to access your web service.
WSWS3329E: Error: The XML Schema type ''{0}'' is not valid in the Schema version ''{1}''.
Explanation
WSDL2Java error.
User Response:
Please correct your wsdl.
WSWS3330I: Info: {0} already exists, WSDL2Java will not overwrite it.
Explanation
WSDL2Java informational message.
User Response:
No action required.
WSWS3331E: Error: Invalid gYearMonth.
Explanation
Error occurred while constructing a YearMonth object.
User Response:
Use a correct value.
WSWS3332E: Error: Invalid gYear.
Explanation
Error occurred while constructing a Year object.
User Response:
Use a correct value.
WSWS3333E: Error: Invalid gMonth.
Explanation
Error occurred while constructing a Month object.
User Response:
Use a correct value.
WSWS3334E: Error: Invalid gDay.
Explanation
Error occurred while constructing a Day object.
User Response:
Use a correct value.
WSWS3335E: Error: Invalid gMonthDay.
Explanation
Error occurred while constructing a MonthDay object.
User Response:
Use a correct value.
WSWS3336E: Error: Invalid duration: must contain a P.
Explanation
Error occurred while constructing a Duration object.
User Response:
Use a correct value.
WSWS3337E: Error: Serializer class {0} does not implement SimpleValueSerializer, which is necessary for attributes.
Explanation
This serializer cannot be used to serialize attributes.
User Response:
Please correct your deployed type mappings.
WSWS3338E: Error: JIMI is necessary to use java.awt.Image attachments (http://java.sun.com/products/jimi/).
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3340E: Error: The OperationDesc for {0} was not syncronized 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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3341E: Error: No service class was found.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3342E: Error: Cannot handle {0}, can only handle JPEG image types.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3343W: Warning: Factory {0} Ignored: missing required method: {1}.
Explanation
Correct your factory implementation.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3344W: Warning: Factory {0} Ignored: invoke method failed: {1}.
Explanation
Invoke method failed.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3345E: Error: Unable to locate a valid EngineConfigurationFactory.
Explanation
Missing factory implementation.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3346E: Error: Factory {0} Ignored: unable to load/resolve class.
Explanation
Cannot load the indicated factory.
User Response:
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3348E: Error: qname attribute is missing.
Explanation
WSDD Deployment information is missing. This may be due to an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3349E: Error: Element {0} is referenced but not defined.
Explanation
WSDL2Java error indicating that an element is referenced but no definition was found.
User Response:
Please correct your wsdl.
WSWS3350E: Error: Missing type or ref attribute for node ''{0}''
Explanation
A type or ref attribute is used to reference a type or element.
User Response:
Please correct your wsdl.
WSWS3351E: Error: Unable to deploy typemapping: {0}
Explanation
This may be due to a deployment problems.
User Response:
Make sure that the indicated class can be found and loaded.
WSWS3352E: Error: Couldn''t find a matching Java operation for WSDD operation "{0}" ({1} args).
Explanation
Normally this indicates a problem with the missing or incorrect deployment information.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3353E: Error: Method style for message-based service wasn't one we recognized.
Explanation
Internal Error. This is an unsupported api.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
Please correct the wsdl.
WSWS3356E: Error: Couldn't find an appropriate operation for XML QName {0}
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3357E: Error: operation description is missing parameter description.
Explanation
Internal Error that may indicate that operation deployment information is missing or incorrect.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
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.
User Response:
Please correct the wsdl.
WSWS3360E: Error: ERROR: Missing element inFault "{0}" in operation "{0}", in binding {1}
Explanation
The binding fault must have a appropriate element.
User Response:
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3362E: Error: Didn''t find specified return QName {0}
Explanation
The response soap message is incorrect.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3363E: Error: The value of the -use option must be LITERAL or ENCODED.
Explanation
The -use option of Java2WSDL is incorrect.
User Response:
Correct the -use option.
WSWS3364E: Error: Invalid class provided for -extraClasses option: {0}
Explanation
The -extraClasses option of Java2WSDL is incorrect.
User Response:
Correct the -extraClasses option.
WSWS3365E: Error: Cannot invoke a oneway call when the call has a return type.
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.
User Response:
Correct the class.
WSWS3366E: Error: The operation must be specified.
Explanation
Probably an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3367E: Error: Failure priming the MessageContext object for operation invocation: {0}
Explanation
Probably an internal error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3369E: Error: The builder {0} does not have a SOAPElement to build.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3370E: Error: Only one SOAPEnvelope is allowed in a SOAPFactory.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3371E: Error: Cannot invoke addChildElement on a {0} object.
Explanation
Cannot add a child SOAPElement to the indicated object.
User Response:
Correct your code.
WSWS3372E: Error: Cannot add a {0} child element to a {1} object.
Explanation
Cannot add the indicated child element.
User Response:
Correct your code.
WSWS3373E: Error: Cannot invoke addTextNode on a {0} object.
Explanation
Cannot add a Text node to the indicated object.
User Response:
Correct your code.
WSWS3374E: Error: Cannot replace SOAPElement's attributes.
Explanation
Cannot call setAttributes after the SOAPElement has attributes.
User Response:
Correct your code.
WSWS3375E: Error: Cannot replace SOAPElement's MappingScope.
Explanation
Cannot call setMappingScope after the SOAPElement has a MappingScope.
User Response:
Correct your code.
WSWS3376E: Error: Don't know how to convert alternate content of class {0}.
Explanation
This is an unrecognized alternate content type.
User Response:
Correct your code.
WSWS3377E: Error: Multiple elements have the name ({0}):{1}.
Explanation
Expecting only one child element of the given qname.
User Response:
Correct your code.
WSWS3378E: Error: Can't set alternate content on a SOAPElement that already has alternate content.
Explanation
An attempt was made to set alternate content on a SOAPElement that already has alternate content.
User Response:
Make sure you remove the existing alternate content before replacing it.
WSWS3379E: Error: Prefix {0} is undefined.
Explanation
The indicated prefix does not have a corresponding namespace uri.
User Response:
Correct your code or soap message.
WSWS3380E: Error: An attempt was made to modify a read-only MappingScope.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3381E: Error: Circular loop encountered while processing MappingScope.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3382E: Error: An unqualified namespace cannot have a prefix. Prefix is {0}.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3383E: Error: Illegal use of xmlns prefix encountered.
Explanation
The soap message has an illegal xmlns prefix.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3384E: Error: Admin process failed.
Explanation
Admin tool failed.
User Response:
The Admin tool is not fully supported.
WSWS3385E: Error: The onStartChild method of {0} did not return a processor.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3386E: Error: Tried to push a null processor.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3387E: Error: An attempt was made to serialize a null object. This should have been handled in the serialize() method.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3388E: Error: Exception generated while rewinding request handlers during fault processing: exception ignored, processing halted.
Explanation
An exception was thrown during handler fault processing.
User Response:
Inspect your handlers.
WSWS3389E: Error: JAXRPC Handler Class {0} not found/loaded, ignored.
Explanation
The indicated class could not be found and/or loaded.
User Response:
Determine why the class was not found or loaded.
WSWS3390E: Error: Load of class {0} failed unexpectedly.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3391W: Warn: {0}.handleRequest returned false and failed to set response message.
Explanation
Warning.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3392E: Error: Unexpected: Unable to create response message on behalf of handler.
Explanation
Warning.
User Response:
This is an unexpected exception. The cause can not be immediately determined.
WSWS3393E: Error: {0}.handlerRequest should not throw javax.xml.rpc.soap.SOAPFaultException on client-side.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3394E: Internal Error: attempted to put {0} into pool of {1}.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3395E: Error: {0}.{1} threw RuntimeException.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
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.
User Response:
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.
User Response:
Correct your handler.
WSWS3399E: Error: {0} ''{1}'' didn't implement ''{2}''.
Explanation
Deployment error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3400I: Info: unexpected exception.
Explanation
Probably an internal problem.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3401E: Error: RequestMessage missing on MessageContext.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3402E: Error: INTERNAL: ResponseMessage missing on MessageContext.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3403E: Error: Unexpected Life Cycle State: current="{0}", expected="{1}".
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3404E: Error: Unexpected: SubSet({0}, {1}, {2}): acting as empty set.
Explanation
Internal Error.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3405I: Info: Ignoring exception thrown by {0}.
Explanation
Informational Message.
User Response:
No action required.
WSWS3406E: Unexpected exception caught while sending reply message: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3407E: Invalid protocol for JMS URL string: {0}
Explanation
The protocol for a JMS URL string should be "jms:"
User Response:
Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.
WSWS3408E: A valid URL string can not be formed from the properties contained in the JMSURLParser object.
Linked exception: {0}
Explanation
The set of properties currently contained within the JMSURLParser object cannot form a valid JMS-style URL string.
User Response:
Make sure that a proper JMS-style URL is passed to the JMSURLParser constructor when the object is constructed.
WSWS3409E: Internal Error: Client/Server mode not set for soap port.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSWS3410E: Invalid value specified for the {0} property.
Explanation
The value supplied for the specified property was not correct.
User Response:
Make sure that you use the correct value for the specified property.
WSWS3411E: Request timeout exceeded.
Explanation
A request did not complete within the specified timeout period.
User Response:
Make sure that your server is active and is able to process requests within the allotted time.
WSWS3412E: A JMS reply message was received which did not correlate with the JMS request message.
Explanation
The JMS correlation id in the reply message did not match the JMS message id in the request message.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
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.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.