MustGather: ODR HTTP Request Routing problems in WebSphere Intelligent Management

Technote (troubleshooting)


Collecting data for problems related to the On Demand Router (ODR) for IBM WebSphere Intelligent Management. Gathering this information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving the problem

If you have already contacted support, continue on to the component specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Intelligent Management.

On Demand Router (ODR) HTTP request routing specific MustGather information

  1. The following outline lists the steps to enable tracing for a set of different components in WebSphere Intelligent Management. This tracing can be pretty verbose and so it is recommended that the size of trace files be increased to 100 MB and the number of history log files to be retained be changed to 10. This will allow the various servers to collect a good sized trace without losing any critical diagnostic information due to log-wrapping.

    For example, to change this setting for the On Demand Router, navigate the following path on the administrative console. Servers -> On Demand Routers -> <odr name> -> Diagnostic Trace service. On this panel, you can change the trace file size and the number of history files.

  2. Enable Tracing for the Deployment Manager process with the following trace string:**=all.

  3. Enable Tracing for the On Demand Router processes with the following trace strings:**=all**=all**=all**=all

    For 504 responses, enable the following tracing:

    WebSphere Proxy=all: GenericBNF=all: HTTPChannel=all.

  4. Stop the Deployment Manager and On Demand Router Processes

  5. Clear out the ..<profile_name>\logs directories for the Deployment Manager and On Demand Router profiles.

  6. Restart the Deployment Manager and On Demand Router processes.

  7. Enable script if tracking down an incorrect Http response.

    The script is added to help diagnose errors returned by the ODR, particularly 404s and 503s. 

    Usage: From the WebSphere_Install_Root\bin directory, execute -lang jython -f setHttpDebug
     my_Node my_ODR Http_error true 2

    my_node the node name that needs to be debugged
    my_odr the name of the ODr that needs to be debugged
    Http_error the Http response that needs to be debugged (ie. 503)

  8. Recreate the error.

  9. Zip up (create a JAR file) the following directories and send the zip (JAR) file.
    1. ../profiles/<profile_where_ODR_runs>/logs/*
    2. ../profiles/<profile_where_ODR_runs>/installedFilters/
    3. ../profiles/<profile_where_DMGR_runs>/logs/*
    4. ../profiles/<profile_where_DMGR_runs>/installedFilters/

    <profile_where_ODR_runs> is the name of the WebSphere Application Server profile where the On Demand Router runs.
    <odr_server_name> is the name of the On Demand Router server.

    <profile_where_DMGR_runs> is the name of the WebSphere Application Server profile where the Deployment Manager runs.
    <odr_server_name> is the name of the Deployment Manager server.

What to do next
Once you have collected the MustGather information simply submit the diagnostic information to IBM support.

Related information

Recording your screen to share with IBM Support

Document information

More support for:

WebSphere Application Server
Intelligent Management Pack

Software version:

6.1, 7.0, 8.0, 8.5.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, z/OS

Software edition:

All Editions

Reference #:


Modified date:


Translate my page

Content navigation