MustGather: WebSphere Extended Deployment V6.1 ODR Request Queuing and dynamic operations

Technote (troubleshooting)


Problem(Abstract)

This document outlines the tasks involved in collecting data for problems with IBM WebSphere Extended Deployment V6.1 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 Extended Deployment.



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 Extended Deployment. 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 Extended Deployment 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:

    *=info: com.ibm.ws.xd.comm.*=all: com.ibm.wsmm.comm.Stats*=all:
    com.ibm.wsmm.comm.NodeStat*=all: com.ibm.wsmm.grm.*=all: com.ibm.ws.xd.workprofiler.*=all: com.ibm.ws.xd.arfm.*=all:
    com.ibm.ws.dwlm.*=all: com.ibm.wsmm.policing.*=all: com.ibm.wsmm.xdglue.*=all: com.ibm.wsmm.rqm.LowDetail=all: com.ibm.ws.dwlm.client.*=off: com.ibm.ws.odr.route.Server=all: com.ibm.ws.odc.nd.ODCTreeImpl$Save=all:com.ibm.ws.odc.xd.Logger=all


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

    Enable tracing on each nodeagent, Extended Deployment agent, and DMgr process:

    For versions of Extended Deployment prior to V6.1.0.3:

    *=info: com.ibm.ws.xd.comm.*=all: com.ibm.wsmm.comm.Stats*=all:
    com.ibm.wsmm.comm.NodeStat*=all: com.ibm.wsmm.grm.*=all: com.ibm.ws.xd.workprofiler.*=all: com.ibm.ws.xd.arfm.*=all:
    com.ibm.ws.dwlm.*=all: com.ibm.wsmm.policing.*=all: com.ibm.wsmm.xdglue.*=all:
    com.ibm.ws.xd.hmm.*=all: com.ibm.ws.xd.admin.utils.*=all: com.ibm.ws.clustersensor.impl.*=all: com.ibm.ws.xd.placement.*=all: com.ibm.ws.xd.placement.brain.*=fine: com.ibm.ws.xd.placement.memory.profiler.impl.*=off: com.ibm.ws.odc.nd.ODCTreeImpl$Save=all:com.ibm.ws.odc.xd.Logger=all

    For versions of Extended Deployment after V6.1.0.3:

    *=info: com.ibm.ws.xd.comm.*=all: com.ibm.wsmm.comm.Stats*=all:
    com.ibm.wsmm.comm.NodeStat*=all: com.ibm.wsmm.grm.*=all: com.ibm.ws.xd.workprofiler.*=all: com.ibm.ws.xd.arfm.*=all: com.ibm.ws.dwlm.*=all: com.ibm.wsmm.policing.*=all:
    com.ibm.wsmm.xdglue.*=all:
    com.ibm.ws.xd.hmm.*=all: com.ibm.ws.xd.admin.utils.*=all: com.ibm.ws.clustersensor.impl.*=all: com.ibm.apc.*=all: com.ibm.apc.brain.*=fine: com.ibm.ws.odc.nd.ODCTreeImpl$Save=all:com.ibm.ws.odc.xd.Logger=all

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

    com.ibm.ws.xd.vv.*=all:com.ibm.ws.vm.*=all:com.ibm.ws.xd.nodedetect.*=all:
    vm.pub=all:com.ibm.venture.*=all

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

    Enable tracing on each WebSphere Application Server:

    *=info: com.ibm.ws.xd.comm.*=all: async.pmi=all: com.ibm.wsmm.grm.model.*=all: com.ibm.ws.sip.container.util.wlm.impl.mop.*=all: detail.com.ibm.ws.sip.container.util.wlm.impl.mop.*=all: com.ibm.ws.sip.container.util.wlm.impl.mop.MOCVerbose=off :com.ibm.ws.xd.arfm.config.*=all:com.ibm.ws.odc.xd.Logger=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.

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

    profile_name/installedFilters/wlm/servername/target.xml

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 Extended Deployment Support page.

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Extended Deployment
Operations Optimization

Translate my page

Machine Translation

Content navigation