WebSphere® system messages are logged from
a variety of sources, including application server components and
applications. Messages logged by application server components and
associated IBM® products start with a unique message identifier
that indicates the component or application that issued the message.
Here is a list of the WSIF runtime system messages, with details of
what each message means.
- WSIF0001E: An extension registry was not found for the element
type "{0}"
- Explanation: Parameters: {0} element type. No extension
registry was found for the element type specified.
- Action: Add the appropriate extension registry to the port
factory in your code.
- WSIF0002E: A failure occurred in loading WSDL from "{0}"
- Explanation: Parameters: {0} location of the WSDL file.
The WSDL file could not be found at the location specified or did
not parse correctly
- Action: Check that the location of the WSDL file is correct.
Check that any network connections required are available. Check that
the WSDL file contains valid WSDL.
- WSIF0003W: An error occurred finding pluggable providers: {0}
- Explanation: Parameters: {0} specific details about the
error. There was a problem locating a WSIF pluggable provider using
the J2SE 1.3 JAR file extensions to support service providers architecture.
The WSIF trace file will contain the full exception details.
- Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF
file exists in the class path, and that each class implements org.apache.wsif.spi.WSIFProvider.
The class in error will be ignored and WSIF will continue locating
other pluggable providers.
- WSIF0004E: WSDL contains an operation type "{0}" that is
not supported for "{1}"
- Explanation: Parameters: {0} name of the operation type
specified. {1} name of the portType for the operation. An operation
type that is not supported has been specified in the WSDL.
- Action: Remove any operations of the unsupported type from
the WSDL. If the operation is required then make sure all messages
have been correctly specified for the operation.
- WSIF0005E: An error occurred when invoking the method "{1}" .
("{0}" )
- Explanation: Parameters: {0} name of communication type.
For example EJB or Apache SOAP. {1} name of the method that failed.
An error was encountered when invoking a method on the web service
using the communication shown in brackets.
- Action: Check that the method exists on the web service
and that the correct parts have been added to the operation as described
in the WSDL. Network problems might be a cause if the method is remote
and so check any required connections.
- WSIF0006W: Multiple WSIFProvider found supporting the same namespace
URI "{0}" . Found ("{1}" )
- Explanation: Parameters: {0} the namespace URI. {1} a list
of the WSIFProvider found.. There are multiple org.apache.wsif.spi.WSIFProvider
classes in the service provider path that support the same namespace
URI.
- Action: A following WSIF0007I message will be issued notifying
which WSIPFProvider will be used. Which WSIFProvider is chosen is
based on settings in the wsif.properties file, or if not defined in
the properties, the last WSIFProvider found will be used. See the
wsif.properties file for more details on how to define which provider
should be used to support a namespace URI.
- WSIF0007I: Using WSIFProvider "{0}" for namespaceURI "{1}"
- Explanation: Parameters: {0} the classname of the WSIFProvider
being used. {1} the namespaceURI the provider will be used to support..
Either a previous WSIF0006W message has been issued or the SetDynamicWSIFProvider
method has been used to override the provider used to support a namespaceURI.
- Action: None. See also WSIF0006W.
- WSIF0008W: WSIFDefaultCorrelationService removing correlator due
to timeout. ID:"{0}"
- Explanation: Parameters: {0} the ID of the correlator being
removed from the correlation service. A stored correlator is being
removed from the correlation service due to its timeout expiring.
- Action: Determine why no response has been received for
the asynchronous request within the timeout period. The wsif.asyncrequest.timeout
property of the wsif.properties file defines the length of the timeout
period.
- WSIF0009I: Using correlation service - "{0}"
- Explanation: Parameters: {0} the name of the correlation
service being used. This identifies the name of the correlation service
that will be used to process asynchronous requests.
- Action: None. If a correlation service other than the default
WSIF supplied one is required, ensure that it is correctly registered
in the JNDI java:comp/wsif/WSIFCorrelationService namespace.
- WSIF0010E: Exception thrown while processing asynchronous response
- "{0}"
- Explanation: Parameters: {0} the error message string of
the exception. While processing the response from an executeRequestResponseAsync
call an exception was thrown.
- Action: Use the exception error message string to determine
the cause of the error. The WSIF trace will have more details on the
error including the exception stack trace.
- WSIF0011I: Preferred port "{0}" was not available
- Explanation: Parameters: {0} the user's preferred port.
The preferred port set by the user on org.apache.wsif.WSIFService
is not available
- Action: None unless this message appears for long periods
of time in which case the user might want to pick a different port
as their preferred port.