IBM Support

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

Technote (troubleshooting)


Problem(Abstract)

Collecting data for problems with the IBM WebSphere Application Server JAX-WS and JAX-RPC Web services engines. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving the 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 calling IBM support will help you understand the problem and save time analyzing the data.


Tab navigation

Read first and related 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 to be used in problem determination. You can submit files 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=enabled:org.apache.cxf.*=all=enabled


WEBSPHERE TRADITIONAL

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

Additional trace string
Final trace string
JAX-WS or JAX-RPC
(base trace)
*=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all
If you see IOException related to Webservice requests :HTTPChannel=all:GenericBNF=all:TCPChannel=all *=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

If you are deploying EAR which has webservices, having issue with generating webservices code and post deployment issue, then enable below trace in Deployment manager process 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

Please 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? Please 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

(for example, trying to install an EAR):
  1. Did this work at one time before changes were made? Please 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 performance tuning custom properties that you have configured.

WS-Security Issues


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

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 Knowledge Center.
      • 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 recreated 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 before starting 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 Knowledge Center.
  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 will 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 will gather 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.

Related information

MustGather: Read first for WebSphere Application Server
MustGather: JAX-WS PolicySet and Bindings
Steps to get support for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server
Tracing web services
Set up trace and get a full dump for Liberty
Liberty Logging and Trace reference
Recording your screen to share with IBM Support
Submitting information to IBM support
HPEL Mode in WebSphere Application Server V8.0

Cross reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK

Document information

More support for: WebSphere Application Server
Web Services (for example: SOAP or UDDI or WSGW or WSIF)

Software version: 7.0, 8.0, 8.5, 9.0

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: Base, Express, Network Deployment

Reference #: 1198363

Modified date: 19 April 2012