IBM Support

MustGather: WebSphere Intelligent Management ODR Request Queuing and dynamic operations



This document outlines the tasks involved in collecting data for problems with IBM WebSphere Intelligent Management functions including the placement controller, autonomic request routing (ARFM) and health management. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving The Problem

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

Request Queuing and dynamic operations specific MustGather information

  • 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 trace files size 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: Troubleshooting -> Logs and Trace -> <odr name> -> Diagnostic Trace service. On this panel, you can change the trace file size and the number of history files.

  • Enable tracing on the Dmgr,nodeAgent and Intelligent Management agent processes:
    1. In the administrative console, go to TroubleShooting > Logs and Trace > server_name > Change Log Level Details.

    2. Select the Runtime tab.

    3. For all running processes:

    Enable tracing on each ODR process:


    The preceding trace string is meant to be one continuous line.

    Enable tracing on each nodeagent, Intelligent Management agent, and DMgr process:

    For versions of Intelligent Management after V6.1.0.3:


    Note - vmware only Please add the following on nodeagent and dmgr processes if running on vm hardware.***=all:*=all

    Note: The preceding trace string is meant to be one continuous line.

    Enable tracing on each WebSphere Application Server:

    *=info:*=all: async.pmi=all:*=all:*=all:*=all:*

    Note: The preceding trace string is meant to be one continuous line.

  • Making changes by navigating to the Runtime tab only affects the currently running server instance. To make this change permanent or to save these changes to the configuration repository so that they are applicable to a server from startup, make changes to the Configuration tab instead. Changes made in this fashion take effect when the server is restarted.

  • Recreate the problem.

  • Run the collector tool on each profile. When you run the collector tool, it creates a jar file with the information about that profile that it was run against, please send us the jar file that the collector tool created.
    If there is a message about the collector tool being deprecated you can ignore it, do not run ISADC tool, the collector tool should continue after a pause in the script.

  • Send in the following:
    1. All the collector tool output files.
    2. Detailed problem description
    3. Steps to recreate

    Collect the following file from all profiles:


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

For a listing of all technotes, downloads, and educational materials specific to the Service Policy component, search the WebSphere Intelligent Management Support page.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"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"},{"code":"PF035","label":"z\/OS"}],"Version":"7.0","Edition":"All Editions"}]

Document Information

Modified date:
15 June 2018