IBM Support

MustGather: JAX-WS/JAX-RPC Web Services engine problems for WebSphere Application Server

Troubleshooting


Problem

Collecting data for problems with the IBM® WebSphere® Application Server Web services engine and tooling components for JAX-WS and JAX-RPC. Gathering this MustGather information before you call IBM support can help you understand the problem and save time analyzing the data.

Resolving The Problem

  • Read first and MustGathers
  • Exchange data with IBM Support

    To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities for you to use during problem determination. You can submit files by using one of following methods to help speed problem diagnosis:


  • Web Services engine trace specifications

    Web services traces that you obtain to send to IBM support must be gathered from server startup.

     

    LIBERTY


    com.ibm.ws.jaxws.*=all:org.apache.cxf.*=all

     

    WEBSPHERE TRADITIONAL

    Trace strings for the WebSphere traditional must be entered as one line with no breaks or spaces.

    JAX-WS and JAX-RPC base trace:

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

    IOExceptions issues:
    If you see IOException related to Webservice requests:

    *=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all:HTTPChannel=all:GenericBNF=all:TCPChannel=all

    Deployment issues:
    If you are deploying an EAR that has a web service and are having an issue with generating webservices code and post deployment, then enable the following trace in deployment manager process:

    *=info:com.ibm.config.eclipse.wtp=finer:com.ibm.ws.ecs=finer:com.ibm.config.annotations=finer:com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all

     
  • Diagnostic questions

    Answer the following diagnostic questions based on the type of problem that you are encountering:

    Runtime Issues

    1. Did this work at one time before changes were made? Explain.
    2. What is the web service client (for example, a servlet running on WebSphere Application Server, a standalone Java™ application, Microsoft® .NET client, and so on)?
    3. What is the web service provider (WebSphere Application Server, .NET, unknown third party)?
    4. Is the failure reported in the logs from the web service client or the web service provider?
    5. When does the problem occur?
    6. How often does the problem occur?
    7. What is the exact URI of the web service that experienced the problem?
     

    Deployment Issues

    1. Did this work at one time before changes were made? Explain.
    2. Does it work when the Deploy web services checkbox is checked?
    3. Does it work when the Deploy web services checkbox is not checked?'
     

    Performance Issues

    1. Does this performance issue occur only when you invoke the web service for the first time or does it occur on every invocation?
    2. How often does this performance issue occur?
    3. List any web service or performance-tuning custom properties that you have configured.
     

    WS-Security Issues

    See MustGather: Web Services Security (WS-Security) problems with WebSphere Application Server and Liberty to complete this task.
  • Collect data for WebSphere traditional
    This section is for collecting data for the WEBSPHERE TRADITIONAL. If you want to collect data for Liberty, see the Collect data for Liberty section below.

    To troubleshoot a web services problem on WebSphere traditional, collect the information in the following table.

    When all the information for your issue is ready, follow the instructions on Exchanging information with IBM Technical Support for problem determination to send the information and files that you collected.

    Web services traces that you obtain to send to IBM support must be gathered from server startup.

     
    Item to collect
    Comments / Instructions
    Problem description Provide a clear, specific problem description, including specific usage information and error scenario.
    Diagnostic questions Answer the diagnostic questions for the type of problem that you are having in the Diagnostic questions section above.
    Simplified test case, EAR file ,or RAD project interchange file Provide a simplified test case that demonstrates the problem.
    Include step-by-step instructions for running the test case.

    If a simplified test case is not available, provide following files:
    • Web Services Description Language (WSDL) file
    • All XML schema files
    Web Services trace

    Required for the following types of issues:
     
    • Runtime
    • Deployment
    Enable web services tracing and reproduce the problem. If possible, enable tracing on both the web service client and the web service provider.

    Avoid trouble: Web Services traces must be gathered from client or application server startup in order to confirm that the components are initialized without error.

    1. Determine your trace specification
    1. Expand the Web Services engine trace specifications section above.
    2. Note the WEBSPHERE TRADITIONAL trace specification.
    3. Expand Collect data for WebSphere traditional to return to these steps.

    2. Enable trace
    • To enable trace on a MANAGED or UNMANAGED CLIENT (launchClient or thinclient):
      1. Follow the instructions in the Tracing web services topic in the IBM Documentation.
        • Use the trace string that you chose in the Determine your trace specification step above.
      2. After enabling trace on your client, proceed to 'Reproduce the problem'

      To enable trace on an APPLICATION SERVER:
      1. In the administrative console, expand Troubleshooting > Logs and Trace > server_name > Diagnostic trace service
      2. Configure the trace file specifications
        1. Under Trace Output, select File
        2. (Optional) Set Maximum File Size and Maximum Number of Historical Files
          • The default values for Maximum File Size and Maximum Number of Historical Files are sufficient if the problem can be re-created with one request. However, if the problem is intermittent, it is necessary to increase the File Size to 200 MB and set an appropriate number of historical files.
        3. Click Apply
      3. Set the trace specification
        1. Click Change log level details
        2. If there is a trace specification in the box, delete it
        3. Enter the web services trace string that you chose in the Determine your trace specification step above.
        4. Click Apply
      4. Click Save
      5. Proceed to 'Reproduce the problem'

    3. Reproduce the problem
    Avoid trouble: Web services traces must be gathered from client or application server startup. On the client or application server on which you are obtaining a trace do the following:

    Ensure that the clocks on the systems hosting your web services provider and consumer are synchronized you start the trace.
    1. Stop the client or application server
    2. Remove or clear the entire log and FFDC directories.
    3. Restart the client or application server
    4. Reproduce the problem

    4. Locate the trace file
    The trace is found in the following location:
    (was_profile_root)/logs/(server_name)/trace*.log

    Follow instructions to send diagnostic information to IBM support to send the files mentioned in the preceding steps.
     
     
  • Collect data for Liberty
    This section is for collecting data for LIBERTY. If you want to collect data for WebSphere traditional, see the Collect data for WebSphere traditional section above.


    To troubleshoot a web services problem on Liberty, collect the information in the following table from the system on which the feature is configured.

    When all the information for your issue is ready, follow the instructions on Exchanging information with IBM Technical Support for problem determination to send the information and files that you collected.

    Traces that you obtain to send to IBM support must be gathered from server startup.

     
    Item to collect
    Comments / Instructions
    Problem description Provide a clear, specific problem description, including specific usage information and error scenario.
    Diagnostic questions Answer the diagnostic questions for the type of problem that you are having in the Diagnostic questions section above.
    Simplified test case or EAR file Provide a simplified test case which demonstrates the problem.
    Include step-by-step instructions for running the test case.

    If a simplified test case is not available, provide following files:
    • Web Services Description Language (WSDL) file
    • All XML schema files
    Web Services trace Enable the web services tracing and reproduce the problem.

    Avoid trouble: Web Services traces must be gathered from Liberty server startup in order to confirm that the component is initialized without error.

    1. Determine your trace specification
    1. Expand the Web Services engine trace specifications section above.
    2. Note the LIBERTY trace specification.
    3. Expand Collect data for Liberty to return to these steps.

    2. Enable trace
    To enable trace on Liberty:
    1. Follow the instructions in the Enabling Trace on Liberty section in Set up trace and get a full dump for WebSphere Liberty.
      • Additional information can be found in the Logging and Trace topic in the IBM Documentation.
    2. Use the trace string that you chose in the Determine your trace specification step above.
    3. Proceed to 'Reproduce the problem'

    3. Reproduce the problem
    Avoid trouble: Web Services traces must be gathered from Liberty server startup. On the Liberty server on which the feature is configured, do the following:

    Ensure that the clocks on the systems hosting your web services provider and consumer are synchronized before starting the trace.
      1. Stop the Liberty server
      2. Restart the Liberty server
      3. Reproduce the problem.

    4. Locate the trace and log files
    In LIBERTY, by default, the trace is found in the following location:

    (wlp.install.dir)/usr/servers/(server_name)/logs

    If you do not see your trace in that directory, you can find the log directory configured on the logDirectory attribute in your server.xml file.

    5. Recursive zip the logs directory
    Perform a recursive zip in the directory identified in the step above and send in the file. This zip gathers the following files:

    * console.log
    * messages.log
    * trace.log
    * ffdc/*

    Liberty Web Services trace specification:
     
    com.ibm.ws.jaxws.*=all=enabled:org.apache.cxf.*=all=enabled
    Follow instructions to send diagnostic information to IBM support to send the files mentioned in the preceding steps.
  •  

    Note:

    This document uses the term WebSphere traditional to refer to WebSphere Application Server v9.0 traditional, WebSphere Application Server v8.5 full profile, WebSphere Application Server v8.0 and earlier, WebSphere classic, traditional WebSphere, traditional WAS, and tWAS.
     

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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":"9.0;8.5;8.0;7.0","Edition":"Base;Express;Network Deployment","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:
31 August 2023

UID

swg21198363