IBM Support

MustGather: JAX-WS PolicySet and Bindings problems with WebSphere traditional

Troubleshooting


Problem

Collecting data for problems with IBM WebSphere® Application Server versions 9.0, 8.5 and 8.0 using JAX-WS PolicySet and Bindings. 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

    MustGather: Read first for WebSphere Application Server and Liberty

    Web services JAX-WS and JAX-RPC problems Web services security (WS-Security) problems

    For a listing of all technotes, downloads, and educational materials specific to the Web Services Security component, search the WebSphere Application Server support portal.


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

    • Service Request (SR)
    • Email
    • FTP to the Enhanced Customer Data Repository (ECuRep)

    Instructions for exchanging information with IBM Support

  • JAX-WS Policy Set and Binding trace specification
    Since some Policy Manager configuration data is emitted in the trace only during application server startup, it is important that traces that you are obtaining to send to IBM support be gathered from server startup.  
    com.ibm.ws.policyset.*=all
  • Package JAX-WS Policy and Binding Data for Analysis
    The JAX-WS Policy and Binding data might be required for analysis by other components such as WS-Security, Reliable Messaging, and JMS. You are asked to package up entire directories so that IBM service personnel can accurately determine the Policy and bindings that your application is using.
     

    Avoid trouble: If at all possible, for this process, use a zip utility to zip the directories. rar and tar files cannot be used with the automated tools for extracting policy and binding files from the packaged files.

    To package the JAX-WS Policy and Binding data for analysis, do the following:
    Generate separate recursive .zip files from each of the following directories, yielding three files:
    • (cellRoot)/PolicySets
    • (cellRoot)/bindings
    • (cellRoot)/applications/(earName)/deployments/(appName)/META-INF
  • Collect data for WebSphere traditional

    Policy Manager problems can be difficult to troubleshoot. In order to aid problem determination, 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.

    Since some Policy Manager configuration data is emitted in the trace only during application server startup, it is important that traces that you are obtaining to send to IBM support 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
    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?
    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. Due to the complex nature of web services security problems, the fastest way for us to resolve your issue is through a test case.
    • If a test case is not available, provide an EAR file from both the Web service provider and Web service client or provide a Project Interchange file exported from Rational® Application Developer.
    JAX-WS WS-Security policy and binding data Follow the directions in the 'Packaging JAX-WS Policy and Binding Data for Analysis' section above to produce the three .zip files that contain your PolicySet and binding data.
    Policy Manager trace Enable Policy Manager tracing and reproduce the problem.

    Avoid trouble: It is important that Policy Manager traces be gathered from client or application server startup in order to confirm that the components are initialized without error.

    1. 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.
        com.ibm.ws.policyset.*=all
        • Use the Policy Manager trace string:
      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 50 MB and set an appropriate number of historical files.
        3. Click Apply
      3. Set the trace specification
        com.ibm.ws.policyset.*=all
        1. Click Change log level details
        2. If there is a trace specification in the box, delete it
        3. Enter the Policy Manager trace string:
        4. Click Apply
      4. Click Save
      5. Proceed to 'Reproduce the problem'
    2. Reproduce the problem
     
    Avoid trouble: It is important that Policy Manager traces be gathered from client or application server startup. On the client or application server on which you are obtaining a trace do the following:
     
      1. Stop the client or application server
      2. Restart the client or application server
      3. Reproduce the problem
    3. Locate the trace file
     
    In WEBSPHERE TRADITIONAL, 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.

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":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF013","label":"Inspur K-UX"}],"Version":"9.0;8.5.5;8.5;8.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 July 2022

UID

swg22008833

Page Feedback