If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
WSIF specific MustGather information:
- What is your environment (client and server platform, software)?
- Description of your problem, including any errors.
- Description of the steps taken to reproduce your problem, if it can be
recreated.
- What is your WSIF version? (see Section A below)
- Provide a trace demonstrating your problem. (see Section B below)
- Provide a trace for any other relevant components.
- Provide the Web Services Definition Language (WSDL) and schema files
you are using.
- What level of wsdl4j.jar are you using? (see Section C
below)
- If you have your own provider or a correlation service, give
details.
- If altered, provide your wsif.properties file.
- If you are using Java™ Message Service (JMS) or Java Naming and
Directory Interface™ (JNDI), give details of your setup.
- If you have reimplemented the mapping conventions class, provide
details.
- Provide a list of all fixes that you have applied.
- Provide a TCPMON trace, if possible. (see Section D below)
- What transport are you using?
- If possible, provide source code or a simple test case that
demonstrates your problem.
Sections:
- For the WSIF version, find the size and date of your wsif.jar
and the location from where you obtained wsif.jar.
- To switch the trace on, if running inside WebSphere Application
Server:
org.apache.wsif.*=all=enabled:com.ibm.wsif.*=all=enabled |
|
If running stand-alone, in your log4j.properties
specify the following settings to trace to wsif.log: |
|
log4j.rootCategory=INFO, CONSOLE,
LOGFILE
log4j.logger.org.apache.wsif.*=DEBUG
log4j.logger.com.ibm.wsif.*=DEBUG
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=wsif.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.Threshold=DEBUG |
|
WSIF uses Apache commons-logging for its messages and
trace. See http://jakarta.apache.org/commons/logging.html
for more information. Commons-logging is an API that wraps various log
implementations. You can configure commons-logging to use other log
implementations, or even your own. So commons-logging.jar must be
on the classpath, and log4j is the default log implementation, although
commons-logging.jar contains other log implementations. You can
configure commons-logging.properties to use a different log
implementation. If using log4j, you configure log4j.properties to
redirect trace and switch it on. The log4j.properties settings
above are only a subset of all possibilities.
For further information at http://ws.apache.org/wsif/developers/trace.html |
|
- To find the level of the wsdl4j.jar, check the
Manifest.mf file within the .jar file, where a WebSphere
Application Server version number is located.
- To obtain a TCPMON trace,
- If your client application is sending requests to port XXXX on your
server, change it to send requests to port YYYY where YYYY is a port not
being used by any application.
- Open a command prompt.
- Make sure that Java is set up.
- Make sure $WAS_HOME/lib/soap.jar is on your
classpath.
- Execute the following command:
java
org.apache.soap.util.net.TcpTunnelGui listenporttunnelhost
tunnelport |
|
Where,
listenport |
is the port that you want the tool to listen on (for
example: YYYY) |
tunnelhost |
is the hostname of the server |
tunnelport |
is the port that the server is listening on (for example:
XXXX) |
|
|
- Run your application.
This will launch a graphical user interface showing two windows. One
window displays traffic from the client to the server, and the other
displays responses. The information from these two windows can be copied
and pasted into another document and then saved.
Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Web Services component, search the WebSphere
Application Server support site. |