IBM Support

MustGather: Problems with the Web Services Invocation Framework (WSIF)

Troubleshooting


Problem

MustGather for WSIF problems with the IBM WebSphere Application Server Web services component. Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.

Resolving The Problem

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:

  1. What is your environment (client and server platform, software)?
  2. Description of your problem, including any errors.
  3. Description of the steps taken to reproduce your problem, if it can be recreated.
  4. What is your WSIF version? (see Section A below)
  5. Provide a trace demonstrating your problem (see Section B below).
  6. Provide a trace for any other relevant components.
  7. Provide the Web Services Definition Language (WSDL) and schema files you are using.
  8. What level of wsdl4j.jar are you using? (see Section C below)
  9. If you have your own provider or a correlation service, give details.
  10. If altered, provide your wsif.properties file.
  11. If you are using Java™ Message Service (JMS) or Java Naming and Directory Interface™ (JNDI), give details of your setup.
  12. If you have re-implemented the mapping conventions class, provide details.
  13. Provide a list of all fixes that you have applied.
  14. Provide a TCPMON trace, if possible (see Section D below).
  15. What transport are you using?
  16. If possible, provide source code or a simple test case that demonstrates your problem.


Sections:
1. For the WSIF version, find the size and date of your wsif.jar and the location from where you obtained wsif.jar.

2. To switch the trace on, if running inside WebSphere Application Server:
org.apache.wsif.*=all=enabled:com.ibm.wsif.*=all=enabled

3. 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

4. WSIF uses Apache commons-logging for its messages and trace. See http://commons.apache.org/logging/ 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.

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.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Web Services (for example: SOAP or UDDI or WSGW or WSIF)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;7.0;6.1;6.0","Edition":"Edition Independent","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21159155

Page Feedback