IBM Support

MustGather: WebSphere® Intelligent Management creation and configuration of the on demand router (ODR)

Troubleshooting


Problem

MustGather information for problems with the creation and configuration of the IBM WebSphere® Intelligent Management On-Demand router (ODR). Before engaging IBM support, review this information to familiarize yourself with the troubleshooting process.

Resolving The Problem

If IBM® support is engaged, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for WebSphere® Intelligent Management.

ODR-specific MustGather information:
If a servlet engine (SRVE) error is displayed in the browser, then it did not originate from the IBM WebSphere® Application Server and not from the ODR.
If there is a blank screen or another non-SRVE error code message, and the failure does not occur going directly to an Application Server, enable the following trace in the ODR. Send the minimum number of requests from your browser so that the error occurs again.

Collect the following information:
  • Description of the problem that includes:
    • Steps to re-create
    • What is the expected behavior
    • What occurs that indicates that there is a problem
    • Client addresses and URL
    • Time that the failure was captured in data provided
  • Enable the following trace on the WebSphere® Deployment Manager process
    com.ibm.ws.odc.*=all: com.ibm.ws.wsgroup.*=all
  • Enable the following trace on the ODR processes
    com.ibm.ws.odc.*=all:com.ibm.ws.wsgroup.*=all:
    com.ibm.ws.proxy.*=all:com.ibm.ws.dwlm.*=all:
    com.ibm.ws.xd.dwlm.client.*=all:com.ibm.ws.xd.comm.*=all:
    com.ibm.ws.xd.work.*=all:com.ibm.ws.classify.*=all:
    com.ibm.wsmm.*=all:com.ibm.ws.genericbnf.*=all:
    com.ibm.ws.http.channel.*=all:com.ibm.ws.tcp.channel.*=all:
    com.ibm.ws.dwlm.client.TargetDescriptorImpl=off
  • Increase the log size to 100MB and historical logs to 10 to prevent the logs from wrapping.
  • Stop the Deployment Manager and ODR processes
  • Clear out the Deployment Manager, ODR logs, and ffdc directories
  • Start the Deployment Manager and ODR processes

  • Note: If the problem is related to an invalid HTTP response, run the odrDebug.py script
    The purpose of the odrDebug.py script is to help diagnose errors returned by the ODR, particularly 404 and 503 errors.

    From the $WAS_HOME\bin directory, enter:
    wsadmin.sh -lang jython -f odrDebug.py setHttpDebug <my_node> <my_odr> <http_error> true 2

    <my_node> is the node_name that needs to be debugged
    <my_odr> is the name of the ODR that needs to be debugged
    <http_error> is the http response code that needs to be debugged (example, 503)

  • Re-create the problem with the ODR.

  • Run the collector tool on each installation.
    • Include the target.xml file from all the nodes with tracing enabled.
      Location of target.xml:
      $WAS_HOME/AppServer/profiles/<profileName>/installedFilters/wlm/<servername>/target.xml

  • Send collected information and files to IBM for diagnostic review.
  • Follow these instructions to send diagnostic information to IBM support.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Intelligent Management Pack","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2020

UID

swg21221275

Page Feedback