TroubleShooting: Performance Monitoring Infrastructure problems for V5.0, 5.1, and 6.0
 Technote (troubleshooting)
 
Problem(Abstract)
Troubleshooting for Performance Monitoring Infrastructure (PMI) problems in IBM WebSphere Application Server. This should help address common issues with this component before calling IBM support and save you time.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data

Steps to help resolve PMI problems
  1. Is your PMI Service enabled?

    To monitor performance data through the PMI interfaces, you must first enable the Performance Monitoring Service through the Administrative Console before restarting the deployment manager, node agent, and the application servers.

    Note: In WebSphere Application Server V5.0, the PMI service is disabled by default on an application server and node agent. In V6.0, PMI is enabled by default.

    To ensure that PMI is enabled, check the SystemOut.log file and make sure that the following message appears during server startup:
    • For V5.0:

      PMIImpl       A PMI0001A: PMI is enabled

    • For V6.0:

      PMIImpl       A   PMON0001A: PMI is enabled

  2. Do you have questions about or problems with the overhead associated with WebSphere Application Server Performance Monitoring Infrastructure (PMI) for V5.0 and V6.0?
    • If yes, please refer to this technote when enabling PMI.

    • If no, continue to Question 3.

  3. After enabling both PMI Metrics and Java™ 2 Security, you are getting an "AccessControlException" in either V5.0 or V6.0 releases?
    • If yes, please see this technote to work around the problem.

    • If no, continue to Question 4.

  4. In WebSphere Application Server V5.0, are you having problem starting the IBM Tivoli® Performance Viewer GUI? Note that in V6.0 and later, the Tivoli Performance Viewer is embedded in the Administrative Console; there is no separate GUI.
    • If yes, follow the steps below.
    • If no, continue to Question 5.

      Check and make sure that connection to the deployment manager, node agent, or the application server being monitored is properly established. See items 8 and 9 in the MustGather document to properly connect to those entities (either local or remote).

      Note:

      Check the parameters used to run Tivoli Performance Viewer. Ensure that you pass the hostname, port number, and JMX connector type if you are not using the defaults (localhost, 8880/8879, and SOAP connector). In a Network Deployment environment, the Tivoli Performance Viewer must connect to the deployment manager SOAP connector port.

      If running the Tivoli Performance Viewer remotely, make sure that you are using the same version of tperfviewer.bat/.sh as your version of WebSphere Application Server. See the steps below on how to check Tivoli Performance Viewer version:
      1. Start TPV from the install_root/bin directory with the tperfviewer.bat or tperfviewer.sh script.

      2. Once Tivoli Performance Viewer has started, go to "Help" --> "About" and check for the version information.

  5. If you are using WebSphere Application Server V5.0, does the RMI connection work but the SOAP connection fails when starting the Tivoli Performance Viewer GUI?
    • If yes, please review this technote.
    • If no, continue to Question 6.

  6. In WebSphere Application Server V5, do you get unexpected PMI0023W messages in your SystemOut.log? For example:

    PMI0023W: Unable to register PMI module due to duplicate name: <name>
    • If yes, please review this technote.
    • If no, continue to Question 7.

  7. In WebSphere Application Server V5.0, do you see PMI0002W warning messages in the SystemOut.log after the application server is restarted but the Tivoli Performance Viewer has not restarted?
    • If yes, the warnings can be safely ignored and the Tivoli Performance Viewer should function well. This happens because some of the PMI submodule names are changed after server restarts but the Tivoli Performance Viewer still queries for the old names.
    • If no, continue to Question 8.

  8. Review the WebSphere Application Server V5.0, V5.1, or V6.0 Information Center, or the WebSphere Application Server Support site for additional information that may help you to resolve the problem.


What to do next
If the preceding troubleshooting steps did not solve your problem, see the MustGather for PMI problems to continue investigation.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > PMI/Performance Tools
Operating system(s): Windows
Software version: 6.0.2
Software edition:
Reference #: 1240258
IBM Group: Software Group
Modified date: Sep 30, 2007