MustGather: Web Services engine and tooling problems for WebSphere Application Server versions 6.1, 6.0, 5.1, and 5.0.
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server versions 6.1, 6.0, 5.1, and 5.0 Web services engine and tooling component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
 
Resolving the problem

Do you want to automate the collection of MustGather data?
You can automatically collect this data using IBM Support Assistant (ISA) Lite - a special offering that contains the data collector component of the IBM Support Assistant Workbench.

For a full range of problem-solving features, install the IBM Support Assistant Workbench - your support workbench for finding answers and solving problems. The workbench contains all the data collection capability of ISA Lite plus much more!



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.


Web services engine and tooling specific MustGather
  1. Please provide a simplified test case that exhibits the problem. Also, please provide instructions for running the test case. Due to the complex nature of Web Services problems, the fastest way for us to resolve your issue is through a test case. Problem determination might be prolonged without a test case.

    If a simplified test case is not possible, please provide the actual application with source code including the Web Services Description Language (WSDL) and all XML schema files packaged as an EAR

  2. Did this work at one time before changes were made? Please explain.

  3. Is this a run-time issue (for example, a server and client interacting)? If so:

    3a. What is the Web Service client (for example, a servlet running on WebSphere, a standalone Java™ application, .NET client, and so on)?

    3b. What is the Web Service provider (WebSphere Application Server, .NET, unknown third party)?

    3c. Is the failure coming from the client or provider?

    3d. When does the problem occur?

    3e. How often does the problem occur?

    3f. Enable web services tracing. This will show us the internal WebSphere Application Server behavior. See Appendix A.

    3g. Gather a TCPMon capture. This will show the actual SOAP messages going across the network. See Appendix B.

    3h. Reproduce the problem with web services tracing and TCPMon tracing turned on.

    3i. Provide a brief description of the application logic & data flow.

    3j. Provide the exact URI of the Web Service that experienced the problem.

    3k. Gather Application Server logs (including the SystemOut.log), trace files (e.g. trace*.log), ffdc files (inside the ffdc folder), and TCPMon output.
  4. Is this a deployment issue (for example, trying to install an EAR)? If so:

    4a. Does it work when the "Deploy Web services" checkbox is checked?

    4b. Does it work when the "Deploy Web services" checkbox is *not* checked?

    4c. Enable web services tracing. See Appendix A.

    4d. Reproduce the problem with web services tracing turned on.

    4e. Gather WebSphere logs (including the SystemOut.log), trace files (e.g. trace*.log), ffdc files (inside the ffdc folder).
  5. Is this a tooling issue (for example, is code being generated)? If so:

    5a. If you are using WebSphere Studio Application Developer or Rational® Application Developer, please provide the version you are using.

    5b. If you are using the command-line tools (WSDL2Java, Java2WSDL), please provide the command you are using and the WSDL file.
  6. Is this a Web services security issue? If yes, follow instructions from "MustGather: Problems using Web services security for all releases of V6.0"

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

Appendix A

Follow these steps to enable the Web service trace. This is only required on the application server which acts as the Web Services provider (the server) or the Web Services consumer (the client), but not on the deployment manager or node agent. If you are not sure where the problem occurs, collect the trace from the both sides - Web Services provider and the Web Services consumer.

Important steps before you re-produce the problem and collect the trace:

  1. Synchronize clocks on all systems (Web Services provider and Web Services consumer).
  2. Clean all current and historical WebSphere Application Server and FFDC logs and traces.

Enabling Web service trace for WebSphere V6.1 and V6
  1. Start WebSphere Application Server.

  2. Open up the administrative console.

  3. Expand Servers > Application Servers > server_name.

  4. Select Diagnostic Trace Service.

  5. Set Maximum File Size to 200 MB and select File radio button in the General properties section. Set appropriate number of historical trace files.

  6. Navigate to Change Log Detail Levels in the Additional properties section.

  7. Clear the current trace string and add the following trace string to the General properties field for general Web services issues:

    For WebSphere V6.0 and V6.1 JAX-RPC Web Services applications when Web Services Feature Pack is NOT installed

    *=info:com.ibm.ws.webservices.*=all


    For WebSphere V6.1 JAX-WS and JAX-RPC Web Services applications when Web Services Feature Pack is installed

    *=info:com.ibm.ws.webservices.*=all:org.apache.axis2.*=all:
    org.apache.axiom.*=all:com.ibm.ws.websvcs.*=all


    Note: The trace string above is meant to be entered on one line. It is shown on multiple lines here so it is easier to read.

  8. Click Apply and Save.

Enabling Web service trace for WebSphere V5.1 and V5
  1. Start WebSphere Application Server.

  2. Open up the administrative console.

  3. Expand Servers > Application Servers > server_name.

  4. Select Diagnostic Trace Service.

  5. Clear the trace string in the Trace Specification field:

    *=all=disabled

  6. Add the following trace string to the Trace Specification field for general Web services issues:

    com.ibm.ws.webservices.*=all=enabled:HTTP_Transport=all=enabled

    Set Maximum File Size to 200 MB and select File radio button in the Trace Output section. Set appropriate number of historical trace files.

  7. Click Apply and Save.


Appendix B: Obtain a TCPMON trace
  1. In the %WAS_HOME%/bin directory, create the following tcpmon script, specific for your platform (tcpmon.bat for Windows, tcpmon.sh for Unix)

    For Windows (tcpmon.bat)

    1 call "setupCmdLine.bat"
    2 "%JAVA_HOME%\bin\java" -Djava.ext.dirs="%WAS_EXT_DIRS%" com.ibm.ws.webservices.engine.utils.tcpmon
    *For v6.1 environment, tcpmon requires <WAS_HOME>/plugins directory in classpath.

6. For Unix (tcpmon.sh):

1 . ./setupCmdLine.sh
2 "%JAVA_HOME%/bin/java" -Djava.ext.dirs="%WAS_EXT_DIRS%" com.ibm.ws.webservices.engine.utils.tcpmon
*For v6.1 environment, tcpmon requires <WAS_HOME>/plugins directory in classpath.

Here are example scripts:
tcpmon.bat tcpmon.sh
  1. From the %WAS_HOME%/bin directory, run your new tcpmon script
  2. Specify the following:

    Listen Port: Port that you want the tool to listen on
    Target Hostname: Hostname of Web service provider
    Target Port: Port of the Web service provider

    Click Add.
  3. Run your application. The information from this window can be saved by clicking Save after running the application testcase.
For more specific information related to using the TCPMonitor, refer to
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/twbs_tracewbscomp.html
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Web Services (for example: SOAP or UDDI or WSGW or WSIF)
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1198363
IBM Group: Software Group
Modified date: Feb 22, 2007