IBM Support

MustGather: RESTful Web Services (JAX-RS) problems for WebSphere Application Server

Troubleshooting


Problem

Collecting data for problems with the IBM WebSphere Application Server RESTful Web services component. Gathering this MustGather information before you call IBM support can help you understand the problem and save time analyzing the data.

Diagnosing The Problem

Collecting data manually

  1. Provide a simplified test case that exhibits the problem.
    Also, provide instructions for running the test case. Due to the complex nature of RESTful 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, provide the actual application with source code associated with the issue along with deployment descriptors used.
     
  2. Did this work at one time before changes were made?
    Explain.
     
  3. Is this a runtime issue (for example, a server and client interacting)?
    If so:
    1. Is the failure coming from the client or provider?
    2. When does the problem occur?
    3. How often does the problem occur?
    4. Are you packaging or referencing third-party or open source .jar files with application? List them if the answer is yes.
    5. Information about JAX-RS implementation (1.1, 1.2, ...) used in application?
       
  4. Provide a brief description of the application logic and data flow.
     
  5. Provide the exact URI of the RESTful web service that experienced the problem.
     
  6. Perform the steps to enable the RESTful web service trace.
    This is only required on the application server which acts as the RESTful web services provider (the server) or the RESTful 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 both sides - RESTful web services provider and the RESTful web services consumer.
 Important steps before you reproduce the problem and collect the trace:
  • Synchronize clocks on all systems (web services provider and web services consumer).
  • Remove or clear the entire WebSphere Application Server log directory and the FFDC directory.
 Enabling RESTful web service trace for WebSphere Application Server V9.0, 8.5, V8.0, V7.0
  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:
    *=info:com.ibm.ws.jaxrs*=all:com.ibm.websphere.jaxrs*=all:org.apache.wink.*=all:org.apache.cxf.*=all
  8. Click Apply and Save.
  9. Run the collector tool on the node that reproduced the issue, this produces a JAR file containing your WebSphere Application Server configuration files, above traces, and other logs that are useful to the WebSphere Application Server support team.
  10. Submit the collector to IBM support for problem determination.

[{"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.5;8.5;8.0;7.0","Edition":"Liberty;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 July 2022

UID

swg22005317

Page Feedback